Dear Wiki user, You have subscribed to a wiki page or wiki category on "Nutch Wiki" for change notification.
The following page has been changed by PiotrKosiorowski: http://wiki.apache.org/nutch/Release_HOWTO The comment on the change is: Updated with svn commands and directory names. ------------------------------------------------------------------------------ - ''This page is prepared for Nutch committers. You need committer rights to create a new Nutch release.'' + ''This page is prepared for Nutch committers. You need committer rights + to create a new Nutch release.'' = Making a release. = - 1. Update version numbers (from X.Y-dev to X.Y) for release in : + 1. Update version numbers (from X.Y-dev to X.Y) for release in: * nutch-default.xml - user agent string - * default.properties + * default.properties - version property - 1. Update CHANGES.txt with release date and if needed add additional changelog entries. + 1. Update CHANGES.txt with release date and (if needed) add additional changelog entries. - 1. Check if docs need update. + 1. Check if documentation needs an update. - 1. Update news. + 1. Update news in {{{src/site/src/dcoumentation/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. Commit all these changes. 1. Make a clean checkout. - {{{svn ...}}} + {{{svn co https://svn.apache.org/repos/asf/lucene/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. + 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." }}} + 1. Copy release tar file to {{{people.apache.org:/www/lucene.apache.org/nutch/release}}}. - {{{svn ...}}} - 1. Deploy to releases. - {{{cp to ...}}} - 1. Wait for release to propagate to mirrors?? - 1. Deploy new site (according to ["Website Update HOWTO"]). + 1. Deploy new Nutch site (according to ["Website Update HOWTO"]). - 1. Update Javadoc on website. - {{{cp to ...}}} + 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. Create version in JIRA for release. + 1. Create version in JIRA for release X.Y. + 1. Wait for release to propagate to main www.apache.org site. = 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 ...}}} - 1. Update version numbers for to A.B-dev in: + {{{ svn copy https://svn.apache.org/repos/asf/lucene/nutch/tags/Release-X.Y \}}} + {{{ https://svn.apache.org/repos/asf/lucene/nutch/branches/Release-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: * nutch-default.xml - user agent string * default.properties 1. Update CHANGES.txt with header for new changes. - 1. Create version in JIRA for development snapshots. + 1. Create version in JIRA for development snapshots (A.B-dev). We can think about using Apache mirrors for future releases [http://www.apache.org/dev/mirror-step-by-step.html?Step-By-Step Step-By-Step Guide to Mirroring Releases] and sign a release.
