openerp-community team mailing list archive

[Mario Arias <the.clone.master@xxxxxxxxx>]

Reason to be for OCB branches is that official ones are not "community 
friendly"...

 * Lots of bugs with even corresponding MPs that are rejected and/or
   ignored...
 * Changes needed to really fix a bug that are not accepted because of
   the "no change to model", but not fixing is worse...
 * Fixes only applied on trunk, that we as community backport to
   previous series.... specially notorious for mostly abandoned V6.1...


As long as we can keep doing these, I don't care about branch/series 
location... Just don't make them useless...


Regards,
-Mario


On 10/25/2013 09:29 AM, Stefan wrote:
> On 10/25/2013 05:26 PM, Stefan wrote:
> > 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.
>
> > 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.
>
> Oh, after reading your message again I think we agree on this ;-)
>
> Cheers,
> Stefan.
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp