Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Return to the NEXUS staging repository. Login, and RELEASE the Nutch repository.

  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 until the release is visible on the release page
  4. update the Nutch website (see nutch-site README how to)
    1. add the new release info to the doap.rdf file (content/doap.rdf), 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
    2. replace the folder content/documentation/javadoc/apidocs/ with the Java API doc folder of the current version
    3. (only if generating the Miredot REST API docs succeeded) copy the Miredot REST API doc folder (remember this can be located in $NUTCH_HOME/target/miredot) into the nutch-site directory cms_site/content/miredot/

    4. update the version numbers on the javadoc page (content/documentation/javadoc/index.md) and the wiki FrontPage

    5. update the links to release packages on the downloads page (content/download.md)
    6. write a short announcement about the new release in the news section (content/news/)

    7. build the Nutch website, verify the changes and deploy the site
  5. Release the version on Jira
  6. (if necessary) prepare announcements regarding CVEs resolved with this release of Nutch, see the Apache security howtos
  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.

...