I agree with Jeff. The time between Beta and GM should ideally by
longer that "several" days (depending on how you define
"several" :) ).
With 2.2, we should consider such terms as "release candidate"
and make things easier for us and the community as well.
So the process is:
-dev -> Beta -> RC -> GA
On Oct 23, 2005, at 9:18 PM, Paul Querna wrote:
As we get closer to the next stable/GA branch, I want to clarify
with everyone how I imagine the process will happen. This isn't
the process that is documented in VERSIONING, but I think it deals
better with the 2.1.x -> 2.2.0 jump.
1) 2.1.N is tagged.
2) 2.1.N is voted on for BETA.
3) Assuming the vote passes, several days after releasing 2.1.N-
BETA, a vote to mark 2.1.N-BETA as Stable/General Availability will
be called for by the 2.1.N Release Manager.
4) If the vote passes, the 2.1.N tag will be copied to 2.2.0. Only
the version numbers will be changed in Subversion. This 2.2.0
tarball will be placed in /dev/dist/ for final sanity voting. This
final vote *should* be used only to verify that the packaging of
the tag is correct. The code is identical to what passed the GA
vote in step 3.
5) 2.2.0 will be released.
Thoughts/Concerns?
Thanks,
-Paul
