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: http://wiki.apache.org/nutch/Release_HOWTO?action=diff&rev1=11&rev2=12 - ''This page is prepared for Nutch committers. You need committer rights - to create a new Nutch release.'' + = Introduction = + ''This page is prepared and maintained for/by Nutch committers. You need committer rights to create a new Nutch release.'' - = Making a release. = + <<TableOfContents(3)>> + = Preparation = + 1. Create a new release in JIRA. If you do not already have these privileges ask your PMC Chair. + 1. 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. + 1. Update KEYS file in current trunk, make sure that you create an Apache Key. If you don't have a key already create one by following [[http://www.apache.org/dev/openpgp.html#generate-key|this]]. + = Making the Release = 1. Update version numbers (from X.Y-dev to X.Y) for release in: - * nutch-default.xml - user agent string + * nutch-default.xml - http.agent.version property - * default.properties - version property + * default.properties - version property and year property - 1. Update CHANGES.txt with release date and (if needed) add additional changelog entries. - 1. Check if documentation needs an update. - 1. Update news in {{{src/site/src/documentation/content/xdocs/index.xml}}} and for main lucene.apache.org site stored at https://svn.apache.org/repos/asf/lucene/site/. The second change may require additional rights. + 1. 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. + 1. Update news in {{{https://svn.apache.org/repos/asf/nutch/site//site/forrest/src/documentation/content/xdocs/index.xml}}} and for the main nutch.apache,org site stored [[https://svn.apache.org/repos/asf/nutch/site/|here]]. There is documentation on how to edit, manage and build the site documentation [[http://wiki.apache.org/nutch/Website_Update_HOWTO|here]] 1. Commit all these changes. 1. Make a clean checkout. - {{{svn co https://svn.apache.org/repos/asf/lucene/nutch/trunk}}}. + {{{svn co https://svn.apache.org/repos/asf/nutch/trunk/}}}. 1. Build it. {{{ant tar}}} 1. Run unit tests. {{{ant test}}} 1. Do basic test to see if release looks ok - e.g. install it and run example from tutorial. 1. Tag it. - {{{svn copy https://svn.apache.org/repos/asf/lucene/nutch/trunk \}}} {{{https://svn.apache.org/repos/asf/lucene/nutch/tags/release-X.Y -m "Nutch X.Y release." }}} + {{{svn copy https://svn.apache.org/repos/asf/nutch/trunk/ }}} {{{https://svn.apache.org/repos/asf/nutch/tags/release-X.Y -m "Nutch X.Y release." }}} 1. Sign it - [[http://www.apache.org/dev/mirror-step-by-step.html?Step-By-Step|Step-By-Step Guide to Mirroring Releases]]. - 1. Make sure your pgp key is listed in https://svn.apache.org/repos/asf/lucene/nutch/dist/KEYS (update site @minotaur /www/www.apache.org/dist/lucene/nutch svn up) + 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 tar file to {{{people.apache.org:/www/www.apache.org/dist/lucene/nutch}}}. + 1. Copy release tar file to {{{people.apache.org:/www/www.apache.org/tags/nutch}}}. 1. Wait 24 hours for release to propagate to mirrors. - 1. Add the new release info to the [[https://svn.apache.org/repos/asf/lucene/nutch/trunk/site/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. + 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]]). - 1. Deploy new main Lucene site (according to [[Website_Update_HOWTO]] but modified for Lucene site - update is to be performed in {{{/www/lucene.apache.org}}} directory). - 1. Update Javadoc in {{{people.apache.org:/www/lucene.apache.org/nutch/apidocs}}}. + 1. Update Javadoc in {{{people.apache.org:/www/nutch.apache.org/apidocs}}}. - 1. Create version in JIRA for release X.Y. 1. 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/lucene/nutch/tags/release-X.Y \}}} + {{{ svn copy https://svn.apache.org/repos/asf/nutch/tags/release-X.Y \}}} - {{{ https://svn.apache.org/repos/asf/lucene/nutch/branches/branch-X.Y \}}} + {{{ https://svn.apache.org/repos/asf/nutch/branches/branch-X.Y \}}} {{{-m "Nutch X.Y release maintenance branch." }}} - 1. Update version numbers for to A.B-dev (assuming A.B is next release number) in: + 1. Update version numbers to A.B-dev (assuming A.B is next release number) in: - * nutch-default.xml - user agent string - * default.properties + * nutch-default.xml - http.agent.version property + * default.properties - version property and year property 1. Update CHANGES.txt with header for new changes. - 1. Create version in JIRA for development snapshots (A.B-dev). + 1. 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 +
