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 ------------------------------------------------------------------------------ 1. Sign the release (see [http://www.apache.org/dev/mirror-step-by-step.html?Step-By-Step Step-By-Step Guide to Mirroring Releases] for more information). * {{{gpg --armor --output dist/apache-solr-X.Y.M.tgz.asc --detach-sig dist/apache-solr-X.Y.M.tgz}}} * {{{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 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. 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. 1. Tag the release: {{{
