← Back to team overview

openerp-expert-framework team mailing list archive

Re: Making our way out from the bloated extra-addons repository

 

On 11/05/2012 07:09 PM, Raphael Valyi wrote:

Also, something important we should do now:
educate the previous extra-addons users and committers about the new branches to avoid the maintenance to happen in the extra-addons instead of using these new branches.

What can we do for that?
1) send summary emails to the communities, I'll do it

2) remove the extracted modules from the extra-addons? That's a bit brutal for the beginners following these branches may be. Something we could do instead could be add some kind of raise an automatic exception when the code of the module is read, something like "that modules moved to branch X, please download and use branch X or delete that code line alternatively if you want to ignore that warning"


Maybe just a commit with the link to new repository can be enough.
Who uses bzr to download the code (most of us) will see the module disappear and of course will check the log. Who uses apps.openerp.com will see an old 'update date' related to extra-addons branch and a more recent date for new branch.

--
Lorenzo Battistini



References