[Solr Wiki] Update of "HowToRelease" by GrantIngersoll

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

Dear Wiki user,

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

The following page has been changed by GrantIngersoll:
http://wiki.apache.org/solr/HowToRelease

------------------------------------------------------------------------------
  	        * {{{gpg --armor --output dist/apache-solr-X.Y.M.zip.asc --detach-sig dist/apache-solr-X.Y.M.zip}}}
                  * /!\ :TODO: /!\  Sign the Maven artifacts.  See https://issues.apache.org/jira/browse/SOLR-776
                  * See the sign-artifacts target in the build.xml and the associated macrodefs in the common-build.xml file.
-         1. Produce one or more release candidates using the steps outlined here, up to the point of actually tagging the release and distributing it.  Ask on solr-dev for reviewers of the release candidates.  When a consensus emerges, build the final release candidate and call a vote.  3 +1 Lucene PMC votes are required for release (see [http://www.apache.org/foundation/voting.html#ReleaseVotes voting]). A Hudson job has been setup to help in creating and hosting Solr Release Candidates (named: "Solr Release Candidate").  Note the Hudson job does not do the signing required in the previous step, so the final release (at least) will need the signing step.
+         1. Produce one or more release candidates using the steps outlined here, up to the point of actually tagging the release and distributing it.  Ask on solr-dev (cc general@lucene.apache.org) for reviewers of the release candidates.  When a consensus emerges, build the final release candidate and call a vote.  3 +1 Lucene PMC votes are required for release (see [http://www.apache.org/foundation/voting.html#ReleaseVotes voting]). A Hudson job has been setup to help in creating and hosting Solr Release Candidates (named: "Solr Release Candidate").  Note the Hudson job does not do the signing required in the previous step, so the final release (at least) will need the signing step.
          1. Now that you have read this, and done it at least once, know that there is an Ant target named prepare-release that takes care of much of this.  You should still validate the docs, etc. and do the necessary checking.  Calling prepare-release will call sign-artifacts.  You will be prompted to enter you Code signing key numerous times, once per artifact that needs to be signed.  This is a very important step.
          1. /!\ :TODO: /!\  Hook in auto verification of signatures, figure out a way to enter the passphrase just once.
  	1. Tag the release: {{{