On 10/25/2013 05:07 PM, "Lionel Sausin, de la part de l'équipe
informatique Numérigraphe" wrote:
It'd be much easier for everyone if you maintain 2 sets of branches :
- a community-maintained branch complying with the bugfix-only policy,
that OpenERP can merge into the core
- the "OCB" branches with the new fields (after all the B means
backport!), based on the bugfix-branch.
Hi Lionel,
thank you for your input. This alternative approach is very valid too,
of course. While in the past I would have said that maintaining two
separate branches would take too much resources from the maintainers, we
would need to have some sort of distinction anyway if we want to
facilitate easy feedback into the official series.
With regards to the 'B' in OCB: backporting bugs and to a lesser extent
also features does not preclude the introduction of schema changes IMHO.
Cheers,
Stefan.
--
Therp - Maatwerk in open ontwikkeling
Stefan Rijnhart - Ontwerp en implementatie
mail: ste...@therp.nl
tel: +31 (0) 614478606
web: http://therp.nl
_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help : https://help.launchpad.net/ListHelp
