Next year release branch 14 can also be created as it follows release branch 13. This policy of having the branch number (and subsequent major release number) *always* match the last two digits of the year it is created in - and thus avoidance of gaps, is limiting us.
If we create a new branch now in order to meet adherence to that policy, it means that we are going to exclude the 60 patches available on the JIRA issues marked as improvement in the upcoming release. Are we sure this is what we want? Creating branches should meet a higher project purpose than just such a policy. Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Fri, Dec 19, 2014 at 7:01 PM, Nicolas Malin <nicolas.ma...@nereide.fr> wrote: > +0 > > I'm neutral, I prefer planed the branch creation like 15.04 instead of > create stable release branch with many synchronize at the begin (so more > work) because some technology swap are in process and enable (and it's good > ! :)). > > Nicolas > > Le 18/12/2014 09:53, Jacopo Cappellato a écrit : > >> Hi all, >> >> >> the end of 2014 is getting closer and it would be nice to have a new >> release branch created before it ends: its name will be "release14.12" >> (14=2014 and 12=December). >> In this way we will have a sequential numbering: 10, 11, 12, 13, 14. >> Pending the discussion on specialpurpose components (exclude them all >> apart from ecommerce as we did in 13.07, include some of them selectively >> etc...) I would temporarily include them all, and when we will have a clear >> plan of action we will adjust the branch accordingly. >> >> Any objections? >> >> Jacopo >> >> >
