couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Couchdb Wiki] Update of "Release_procedure" by NoahSlater
Date Mon, 31 Oct 2011 18:42:17 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification.

The "Release_procedure" page has been changed by NoahSlater:
http://wiki.apache.org/couchdb/Release_procedure?action=diff&rev1=74&rev2=75

  
  Please try to make it a good one though!
  
- A vote can only pass if three committers give a +1 vote. The PMC is not required to vote,
although it is preferable. This is a safety feature to make sure that a release is not made
when all the committers are away at a conference, or something similar. A vote from a committer
is called a binding vote. All other votes are non-binding, but that does not mean they are
unimportant. If anyone, including a non-committer, gives a -1 vote, then that should be addressed
before proceeding. The aim of the vote is to build community consensus around a release. And
anyone who votes, is by definition, a member of the community. Please note, however, that
all votes should come with a valid rationale.
+ A vote can only pass if there are at least three +1 votes. These votes can come from anyone,
including non-committers, and in fact, everyone is encouraged to partake in and vote on each
release. However, it is preferable that at least three +1 votes come from the committers,
or better yet, the PMC. Once three +1 votes have been counted, the vote can pass. However,
if anyone votes -1 or expresses any serious concern, that should be addressed. Usually, this
will be cause to abort the vote. A vote can only be closed after three working days. This
allows most people a chance to test and vote on the release.
  
  === Making the Release ===
  

Mime
View raw message