|
From: Peter J. <pet...@gm...> - 2011-11-23 09:54:49
|
On Wed, Nov 23, 2011 at 7:23 AM, sfeam (Ethan Merritt) <eam...@gm...> wrote: > Hi all, [...] > - Last time we put out a testing version (release candidate) prior to > releasing 4.4.0. There were some fairly serious problems picked up > by people testing the release candidate. This is a strong argument for putting out a release candidate this time as well. > But recently we have been > getting a lot of feedback from people using the development version > itself, much more then we had prior to releasing 4.4. So we may > not need a separate pre-release testing version this time. > What do you think? > If we anticipate that most of the problems with the 4.6 branch will have been already caught by the people using the development version by the time of the release, we could perhaps shorten the wait time before the "real" 4.6.0 release, but I'd say we shouldn't skip the RC. > The option is still on the table to name the next release 5.0 rather > than 4.6. If you care, please speak up. I vote 4.6 (assuming there is a vote and I can participate in it). There was a long list of issues that could or should be fixed in a potentially compatibility-breaking way. However, I doubt that there is enough time (both in the sense of wallclock time and programmer time) to actually implement and test these fixes before the targeted release date. (Unless we want to do a Linus and follow the current versioning fashion...) > > Ethan Péter Juhász |