Differences between revisions 25 and 26
Revision 25 as of 2013-06-27 17:33:54
Size: 4525
Comment:
Revision 26 as of 2013-06-27 17:53:32
Size: 4418
Comment:
Deletions are marked like this. Additions are marked like this.
Line 35: Line 35:
        1. Make sure your pgp key is listed in https://svn.apache.org/repos/asf/nutch/tags/release-X.Y/KEYS (update site @minotaur /www/www.apache.org/tags/nutch svn up)
 1. Copy release arti
facts to {{{people.apache.org:/www/www.apache.org/tags/nutch}}}.
        1. Create and open a VOTE thread on user@ and dev@nutch.apache.org. The VOTE must pass with 3 +1 binding VOTE's.
        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 dev@nutch.apache.org. The VOTE must pass with 3 +1 binding VOTE's before any release can take place.

Introduction

This page is prepared and maintained for/by Nutch committers. You need committer rights to create a new Nutch release.

Preparation

  1. Make a branch trunk or 2.x as follows
    • svn copy https://svn.apache.org/repos/asf/nutch/${path-to-release}  https://svn.apache.org/repos/asf/nutch/branches/branch-X-Y -m "Nutch X.Y branch" 

  2. Create a new release in JIRA. If you do not already have these privileges ask your PMC Chair.
  3. Push off all open issues to the next release; any critical or blocker issues should be resolved on mailing list. Discuss any issues that you are unsure of on the mailing list.

Prepping the Release Candidate

  1. From now on, use the branch created above.
  2. Update version numbers (from X.Y-dev to X.Y) for release in:
    • nutch-default.xml - http.agent.version property
    • default.properties - version property and year property
  3. Update CHANGES.txt with release date and (if needed) add additional changelog entries. It's also good practice to include a link to the Jira report.
  4. Check if documentation needs an update. Although this may be a huge task at any given time, any minor contribution is better than nothing at all.
  5. Commit all these changes.
  6. Make a clean checkout.
  7. Build it.
    • ant tar

  8. Run unit tests.
    • ant test

  9. Do basic test to see if release looks ok - e.g. install it and run example from tutorial.
  10. Get hold of maven-ant-tasks-2.X.X.jar from here and put it in the ivy directory

  11. Execute ant -lib ivy deploy from $NUTCH_HOME, this will sign the Maven artifacts (sources, javadoc, .jar) and send them to a Apache Nexus staging repository. Details of how to set this up can be found here.

  12. Once you've read, and are happy with the staging repos, close it.
  13. Remove the maven-ant-tasks jar from the ivy directory
  14. If you do svn status, you will see that pom.xml has been updated. Commit this.
  15. Tag it.
    • svn copy https://svn.apache.org/repos/asf/nutch/branches/branch-X-Y  https://svn.apache.org/repos/asf/nutch/tags/release-X.Y -m "Nutch X.Y release." 

  16. run tar-bin, zip-bin, zip-src and tar-src (if releasing trunk) and only the latter two if releasing 2.X (this is because 2.x is only released as source.).

  17. Sign it all of the generated artifacts - Step-By-Step Guide to Signing Releases N.B. an md5, sha and asc should accompany each release artifact.

  18. Make sure your pgp key is listed in the Nutch KEYS file located at http://www.apache.org/dist/nutch/KEYS

  19. Create and open a VOTE thread on user@ and dev@nutch.apache.org. The VOTE must pass with 3 +1 binding VOTE's before any release can take place.

Making the Release

  1. Wait 24 hours for release to propagate to mirrors.
  2. 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

  3. Deploy new Nutch site (according to Website_Update_HOWTO).

  4. Update Javadoc in people.apache.org:/www/nutch.apache.org/apidocs.

  5. Send announcements to the user and developer lists.

Preparing for new development

  1. If needed create a branch for release maintenance(can be done when first commit to branch would be needed).
    •  svn copy https://svn.apache.org/repos/asf/nutch/tags/release-X.Y \  https://svn.apache.org/repos/asf/nutch/branches/branch-X.Y \ -m "Nutch X.Y release maintenance branch." 

  2. Update version numbers to A.B-dev (assuming A.B is next release number) in:
    • nutch-default.xml - http.agent.version property
    • default.properties - version property and year property
  3. Update CHANGES.txt with header for new changes.
  4. Ensure that a new version in JIRA exists for development snapshots (A.B-dev). If this is not there then create one.

Good Luck :)

<<<FrontPage

Release_HOWTO (last edited 2015-01-09 08:36:08 by LewisJohnMcgibbney)