From: Borut R. <bor...@gm...> - 2011-06-05 14:51:58
|
On 06/05/2011 03:17 PM, Philipp Klaus Krause wrote: > Since IMO, the 3.0.0 release didn't go very well¹ I would like to > propose a slight change of release schedule for our next release: > > 1) Some time to fix bugs once we know the freeze deadline (as before) > 2) Freeze (as before) > 3) RC1 a few days after the freeze (as before) > 4) If no grave bugs are found in the current RC within a week, we > release it as 3.1.0, otherwise we make another RC and iterate here. > 5) We make a stable branch from the 3.1.0 release. > 6) A month later or so we make another release from the stable branch. This means that we have to make a release svn branch, which I was trying to avoid in the past... How would you call this two releases? You have to call them differently in order to distinguish them. So the first one will be "pre-release" and the second one will be "release". But the users will again not install the "pre-release" since they will be wainting for the final "release". And this is exactly where we are now, just rename "pre-release" to RCx. > Many people won't try a RC, but they will try something called a > "release". With my schedule proposal we would get more testing exposure > and the second release, that comes after the 3.1.0 release (and that is > the one that will be current for another year or so) would be more stable. Not many users are willing to install a "pre-release" if they know that the release will be available in few weeks. Maybe we shouls invite them more aggressively to test the release candidates instead of complicating the release process, which IMHO will not bring the expected results. This is just my opinion and I may be totally wrong... Borut > Philipp > > ¹ For the Z80 port the situation was like this: No open bugs before > freeze; RC1 went by, RC2 went by, no bugs were found in the Z80 port. > After the release bug reports started coming in. About a month after the > release I had them all fixed in trunk. Thus by then trunk was much more > stable and less buggy than the release. > ¹ The situation will be like this ;-): No open bugs before freeze; RC1 went by, RC2 alias "pre-release" want by, no bugs were found in the Z80 port. After the release bug reports started coming in. About a month after the release I had them all fixed in trunk. Thus by then trunk was much more stable and less buggy than the release. P.S.: On my opinion the solution in such situation is to make an other release as soon as the most critical bugs are fixed. |