sebb wrote on Monday, March 19, 2007 3:09 PM: > On 19/03/07, Vadim Gritsenko <[EMAIL PROTECTED]> wrote: >> sebb wrote: >>> Surely voting on creating a tag (if this is necessary) >> >> Absolutely. Any release tag must be a community decision == vote is >> required. >> >> >>> is completely different from voting on a release? >> >> Not to me. >> >> Voting on a release (on a tag) signifies that software is in a state >> where it can be released to general public. >> >> Voting on a files (produced from release tag) is a mechanical vote on >> correctness of files produced by ant. >> > > AFAIK, the ASF rules are that files must not be released to the > general public without a formal vote by the PMC on the release, which > I take to mean voting on the files which are proposed to be released. > > Requiring consensus on tagging seems sensible, but I'm not > sure it is required. > > The problem here seems to be that it is not possible to use one vote > to do both; therefore it seems to me that the sensible thing to do is > to have two votes. > > The first vote (on tagging) seems to me to be something that relates > mainly to committers working on the project. > > The second vote has to involve PMC members; others can vote, but their > votes generally do not count (though I guess a -1 would need to be > investigated).
And since no-one wants to vote twice, the vote is done on the released artifacts in the RM's private area (or a more official staging area). This includes also that the version is already tagged. If for whatever reason the vote does not pass we can drop the version from the SCM again ... since it did not represent a valid release anymore. > Seems to me that there needs to be formal documentation of the > required and recommended release processes. - Jörg BTW: I did not vote, exactly because I should have to check out from svn - and nobody can guarantee me that I have a proper environment to check the release I build myself. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
