[Spamassassin Wiki] Update of "ReleasePolicy" by SidneyMarkowitz

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

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

The "ReleasePolicy" page has been changed by SidneyMarkowitz:
https://wiki.apache.org/spamassassin/ReleasePolicy?action=diff&rev1=16&rev2=17

Comment:
Fix outdated link, also change other http links to https

  == Core documents ==
  
- We follow the [[http://www.apache.org/foundation/voting.html|Apache Voting Procedure]] with the below modifications.
+ We follow the [[https://www.apache.org/foundation/voting.html|Apache Voting Procedure]] with the below modifications.
- In addition, the PMC has defined as policy that the [[http://cvs.apache.org/viewcvs.cgi/spamassassin/trunk/build/README?root=Apache-SVN&view=markup|build/README release procedure]] must be followed when making a release (it defines the !SpamAssassin release process in great detail).
+ In addition, the PMC has defined as policy that the [[https://svn.apache.org/repos/asf/spamassassin/trunk/build/README|build/README release procedure]] must be followed when making a release (it defines the !SpamAssassin release process in great detail).
  
  == Who can make a release? ==
  
@@ -81, +81 @@

  prior to publication of a release and request a revote.  In addition, the RM 
  may decide against making a release even if the required votes have been made.
  
- Full (general availability) releases require 3 +1's from PMC members and the release can be made as soon as a minimum quorum of three +1's from PMC members is met.  See [[http://www.apache.org/foundation/voting.html|Apache Voting Procedure]].
+ Full (general availability) releases require 3 +1's from PMC members and the release can be made as soon as a minimum quorum of three +1's from PMC members is met.  See [[https://www.apache.org/foundation/voting.html|Apache Voting Procedure]].
  
- Pre-releases and RC's can be created and uploaded with just "lazy consensus" -- ie.  it's all go unless someone speaks up to object.  However, you need to make it clear they are not equivalent to a "full"/"official" release -- they cannot be uploaded to the "real" website download directories (ie www.apache.org/dist), or announced as a full release via a mail to the announce list.  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/ -- for download.
+ Pre-releases and RC's can be created and uploaded with just "lazy consensus" -- ie.  it's all go unless someone speaks up to object.  However, you need to make it clear they are not equivalent to a "full"/"official" release -- they cannot be uploaded to the "real" website download directories (ie www.apache.org/dist), or announced as a full release via a mail to the announce list.  Make it clear that this is an unofficial "test build" by placing it in your public_html dir -- e.g. https://people.apache.org/~jm/devel/ -- for download.
  
  == Oops.  We found a problem ==