On 12/21/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
My understanding was: a) Proposed artifacts land in staging repo b) We vote before cp'ing to rsync repo and dist/ -- release vote c) We have atleast one 'quality' vote, after sufficient time Correct? Is there an announcement after (b), or do we wait till (c)?
That's how it seemed to happen last time, but IIRC we never had a quality vote for Shale 1.0.3. http://mail-archives.apache.org/mod_mbox/shale-dev/200608.mbox/[EMAIL PROTECTED] "If it passes, we'll hold a quality vote later on." IMO, if we're voting on release quality, then every release needs to have a quality attached before it is offered to the public. So b) would default to a vote for alpha quality. It's up to the release manager, though. It could start at beta, or if it's a bugfix on a stable branch and we're confident in the build and release process, it could be voted GA immediately. -- Wendy
