Page History

...

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.

2. In the instance where the VOTE does not pass, the release manager should roll bak back all of the work above as well as DROP the staging artifacts.

...

1. head back over to the staging repos and RELEASE them into the wild.

2. Move the artifacts from the release management area to the release area 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 $release.version" 

3. Wait 24 hours for release to propagate to mirrors.

4. Add the new release info to the 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 here

5. Publish new site as per the documentation within the site readme

   1. copy the Java API doc folder into the svn directory cms_site/content/apidocs/apidoc-X.X and commit it

   2. copy the Miredot REST API doc folder (remember this can be located in $NUTCH_HOME/target/miredot) into the svn directory cms_site/content/miredot/X.Y and commit it

   3. update the links to the new Java API doc in javadoc.html and the wiki FrontPage

   4. update the links to release packages on the downloads page

   5. place a note about the new release on the main page

6. Release the version on Jira

7. Send announcements to the user and developer lists as well as announce@apache.org

8. Finally, don't forget to remove the previous release from dist.apache.org to reduce the load on ASF mirrors, see when-to-archive and NUTCH-1742.

...