I have the impression that the situation is not a tipical git workflow, since the 7.0 branch is not version 7.0 of the addons, but contains addons for version 7.0 of odoo.
For that reason, probably it is more sane to call the branches targeting the future v8 8.0 even if that version does not exist yet. Another option could be to always use the same branch name of core odoo. In that case, we would have "master" to go with odoo master, and when odoo/odoo will create a 8.0 branch we do the same. I am not sure about which one I prefer :) On Wed, Jul 2, 2014 at 3:23 PM, Daniel Reis <[email protected]> wrote: >> I thought it targets the NEXT one and the next one will be V8 when >> published. > > > Yes, right now we have "7.0" for current stable, and "master" for next > version (v8). > > But what happens after v8 is released? > We keep an convention that in the future "master" means last stable? > > If so when v9 is about to be released, precursory migration should go in > feature branches (since "master" is for v8 stable). And the "8.0" branch > would only be created when v9 is released... > > > /DR > > > _______________________________________________ > Mailing list: https://launchpad.net/~openerp-community > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openerp-community > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
