Re: [Dolibarr-dev] 3.2 frozen for any new features

[Laurent Destailleur (eldy)]

Sorry.
A beta is a beta.
Adding something else means all time spent by tester to guarante that 
everything is stable must be started again.
We can't always add new features or add complement on a frozen version.
Any change, even minor that is a new feature breaks stability.
Just an example, 60% of time I spent to make beta 3.0 and 3.1 stable was 
spent to restore stability by forbidden adding feature or architecture 
change. This is not acceptable. This rate should be 0%.
Any change that are not fix will be discarded if it is not to fix a bug, 
translation or documentation.


Le 11/04/2012 12:32, Régis Houssin a écrit :
> yes but no, they are commits that complement the current dev, we'll
> still end up with 3.2 sloppy, they should be able to include minor
> additions in this 3.2
>
>
> Le 11/04/12 11:00, Laurent Destailleur (eldy) a écrit :
> > Hi Dolibarr developers.
> >
> > I revert some changes into the 3.2 branch because they were introducing
> > new features.
> > Absolutely no change must be done into the 3.2 branch, except if a bug
> > is found and change must fix only the found bug.
> > Code normalizing and new features must be push using github into the
> > develop branch only.
> Cordialement,

--
Eldy (Laurent Destailleur).
---------------------------------------------------------------
EMail: address@hidden
Web: http://www.destailleur.fr

Dolibarr (Project leader): http://www.dolibarr.org
To make a donation for Dolibarr project via Paypal: address@hidden
AWStats (Author) : http://awstats.sourceforge.net
To make a donation for AWStats project via Paypal: address@hidden
AWBot (Author) : http://awbot.sourceforge.net
CVSChangeLogBuilder (Author) : http://cvschangelogb.sourceforge.net