We've always gone by the 72 hr rule (in whirr and other projects I'm on): http://incubator.apache.org/guides/releasemanagement.html#glossary-release-manager
However I notice that there's no such mention in the release faq: http://www.apache.org/dev/release.html#approving-a-release Although it does talk about it here: http://www.apache.org/foundation/voting.html I'd suggest we go with the 72 hr rule. Might be a good idea to codify the rules with explicit bylaws like pig/zk and others have done: http://zookeeper.apache.org/bylaws.html (see the bottom of that page) Patrick On Wed, Dec 14, 2011 at 3:03 PM, Andrei Savu <[email protected]> wrote: > +1 > > The only difference from RC0 is: > https://issues.apache.org/jira/browse/WHIRR-449 > > Can we move forward and make the release public as soon as we get 3 > +1's from PMC? > > On Thu, Dec 15, 2011 at 1:02 AM, Andrei Savu <[email protected]> wrote: >> This is the second release candidate for Apache Whirr, version 0.7.0. >> >> It fixes the following issues: >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311110&version=12317571 >> >> *** Please download, test and vote by December 19. >> >> Note that we are voting upon the source (tag), binaries are provided >> for convenience. >> >> Source and binary files: >> http://people.apache.org/~asavu/whirr-0.7.0-candidate-1/ >> >> Maven staging repo: >> https://repository.apache.org/content/repositories/orgapachewhirr-339/ >> >> The tag to be voted upon: >> http://svn.apache.org/repos/asf/whirr/tags/release-0.7.0 >> >> Whirr's KEYS file containing PGP keys we use to sign the release: >> http://svn.apache.org/repos/asf/whirr/dist/KEYS
