You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by Apache Wiki <wi...@apache.org> on 2005/11/18 06:26:23 UTC

[Spamassassin Wiki] Update of "ReleasePolicy" by JustinMason

Dear Wiki user,

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

The following page has been changed by JustinMason:
http://wiki.apache.org/spamassassin/ReleasePolicy

The comment on the change is:
update to match ASF rules

------------------------------------------------------------------------------
  communication, it is deemed polite to alert the community with your
  planned release schedule before executing the release.  A release should
  only be made when there is a plan to publicly release it.  (A release
- should not be made only for private distribution.  A private release is
+ should not be made only for private distribution.  A snapshot is
  more suitable for that.)
  
  == When do I know if it is a good time to release? ==
@@ -75, +75 @@

  
  == Who can vote? ==
  
- Non-committers may cast a vote for a release's quality.  In fact, this
+ Non-committers may cast a vote for a release's quality.  In fact, this is
- is extremely encouraged as it provides much-needed feedback to the
+ extremely encouraged as it provides much-needed feedback to the community about
+ the release's quality.  However, only votes cast by committers count towards
+ the designation.  Note that no one may veto a release.  The PMC or the release
+ manager may revoke all votes on a release if a new major problem is discovered
+ prior to publication of a release and request a revote.  However, once there
- community about the release's quality.  However, only binding votes
- casted by committers count towards the designation.  Note that no one
- may veto a release.  The PMC or the release manager may revoke all votes
- on a release if a new major problem is discovered prior to publication
- of a release and request a revote.  However, once there are greater than
- 3 positive votes, the release may be made at any time.  In addition, the
+ are greater than 3 positive votes, the release may be made at any time.  In
- RM may decide against making a release even if the required votes have
+ addition, the RM may decide against making a release even if the required votes
- been made.
+ have been made.
+ 
+ Full (general availability) releases require 3 +1's from PMC members.  This is
+ unfortunate, but it's a requirement of the ASF's bylaws.
+ 
+ Pre-releases and RC's can be created and uploaded with just committer votes --
+ but they cannot be uploaded to the "real" website download directories.
+ Instead, make it clear that this is an unofficial "test build" by placing it in
+ your public_html dir, e.g. http://people.apache.org/~jm/devel/ .
  
  == Oops.  We found a problem ==