Dear Wiki user, You have subscribed to a wiki page or wiki category on "Nutch Wiki" for change notification.
The "Release_HOWTO" page has been changed by LewisJohnMcgibbney: https://wiki.apache.org/nutch/Release_HOWTO?action=diff&rev1=29&rev2=30 -rw-rw-r-- 1 mary mary 222 Mar 1 14:23 apache-nutch-1.8-src.zip.sha }}} 1. Make sure that '''all artifacts are editable by fellow committers''' e.g. chmod 775 - 1. Check out the release management area at https://dist.apache.org/repos/dist/dev/nutch/ and copy all artifacts to here then commit this. + 1. Check out the release management area at https://dist.apache.org/repos/dist/dev/nutch/{release.version} and copy all artifacts to here then commit this. 1. Make sure your pgp key is listed in the Nutch KEYS file located at http://www.apache.org/dist/nutch/KEYS - 1. Create and open a VOTE thread on user@ and [email protected]. The VOTE must pass with 3 +1 binding VOTE's before any release can take place. + 1. Create and open a VOTE thread on user@ and [email protected]. The VOTE must pass with 3 +1 binding VOTE's before any release can take place. A VOTE thread usually takes the form + {{{ + Hi user@ & dev@, + + This thread is a VOTE for releasing Apache Nutch 1.8 RC#2. The release candidate comprises the following components. + + * A staging repository [0] containing various Maven artifacts + * A branch-1.8 of the trunk code [1] + * The tagged source upon which we are VOTE'ing [2] + * Finally, the release artifacts [3] which i would encourage you to verify for signatures and test. + + You should use the following KEYS [4] file to verify the signatures of all release artifacts. + + Please VOTE as follows + + [ ] +1 Push the release, I am happy :) + [ ] +0 I am not bothered either way + [ ] -1 I am not happy with this release candidate (please state why) + + Firstly thank you to everyone that contributed to Nutch. Secondly, thank you to everyone that VOTE's. It is appreciated. + + Thanks + Lewis + (on behalf of Nutch PMC) + + p.s. Here's my +1 + + [0] https://repository.apache.org/content/repositories/orgapachenutch-1001/ + [1] https://svn.apache.org/repos/asf/nutch/branches/branch-1.8 + [2] https://svn.apache.org/repos/asf/nutch/tags/release-1.8RC%232/ + [3] https://dist.apache.org/repos/dist/dev/nutch/ + [4] https://dist.apache.org/repos/dist/dev/nutch/KEYS + }}} + 1. Once the 72 hour period expires it is time to close the VOTE thread with a RESULT thread. This should simply state the outcome of VOTE'ing (including how many binding VOTE's were received. Finally it should included whether the VOTE passed and if the released can be made. + 1. In the instance where the VOTE does not pass, the release manager should roll bak all of the work above as well as '''DROP''' the staging artifacts. == Making the Release == + 1. head back over to the [[https://repository.apache.org/|staging repos]] and '''RELEASE''' them into the wild. + 1. Move the artifacts from the release management area at https://dist.apache.org/repos/dist/dev/nutch/{release.version} to https://dist.apache.org/repos/dist/release/nutch/{release.version} as follows {{{svn mv https://dist.apache.org/repos/dist/dev/nutch/{release.version} https://dist.apache.org/repos/dist/release/nutch/{release.version} --message "Release Apache Nutch 1.X" }}} 1. Wait 24 hours for release to propagate to mirrors. 1. Add the new release info to the [[https://svn.apache.org/repos/asf/nutch/site/publish/doap.rdf|doap.rdf]] file, and double check for any other updates that should be made to the doap file as well if it hasn't been updated in a while. If this is the case please see [[http://projects.apache.org/doap.html|here]] 1. Deploy new Nutch site (according to [[Website_Update_HOWTO]]).
