On 14.10.2007, at 17:01, Roland Weber wrote:

...
I recently found this Apache page describing release labels:
http://www.apache.org/dev/release.html#release-typeso

Hmm, this part of the page is nice and dandy but the versioning schemes across all ASF project are not really consistent so it's IMHO pretty useless :-/

It seems that our use of "Release Candidate" for something
between beta and final is not the intended interpretation.

Actually I believe a lot of ASF projects are using the -rcX suffix exactly for that purpose and I think that makes more sense than using it for un-approved releases (which simply should be put into tlp.a.o/ dev/dist/ and never into a.o/dist/ - the name is irrelevant, just not voted-on/approved and not released to the general public).

What are we going to do about it?

a) ignore it and continue to use the label as before
b) find a new label between beta and final
c) have betas until we're final

I'm -0 on a, but have no preference among b and c.

I see no problems with a) and c). b) is pretty confusing if there's no page describing the new label ;-)

IMO the above page should be changed to clarify that the term "release candidate" is ambiguous and is used in several ways, e.g.:

1) approved release candidates:
   public candidates which will soon be released as a major milestone,
e.g. foo-1.0-rc1, 1.0-rc2, ..., will soon become foo-1.0 after enough feedback about its "fitness" has been gathered from the public community

2) unapproved releases candidates:
   "non-public" candidates distributed only to developers to vote on,
e.g. foo-1.0 in tlp.a.o/dev/dist/, will soon become foo-1.0 in a.o/dist/
   after it got approved by the developers

2) is what HTTPD is usually doing - there's no -rcX, the name is identical to the final release and it's just a candidate on which the developers are voting. After the candidate got approved it's simply moved over to a.o/dist/, or re-rolled if the vote wasn't successful etc.

Confusing, eh... ;-)

Cheers,
Erik


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to