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: https://wiki.apache.org/nutch/Release_HOWTO?action=diff&rev1=49&rev2=50 1. 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 - 1. 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. + 1. Update CHANGES.txt with release date and (if needed) add additional changelog entries (from Jira Report). It's also good practice to include a link to the Jira report. 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. Commit all these changes. + 1. Commit all these changes to the branch you are releasing. 1. Make a clean checkout. 1. Run unit tests. {{{ant test}}} @@ -25, +25 @@ 1. Once you've read, and are happy with the [[https://repository.apache.org/|staging repos]], close it. 1. Run {{{ant -lib ivy restdocs}}} this builds us some kick ass REST documentation courtesy of our good friends over at [[http://www.miredot.com/|Miredot]] which we can post along with the release. If all builds well then the REST documentation can be located within '''$NUTCH_HOME/target/miredot''' 1. Remove the maven-ant-tasks jar from the ivy directory - 1. If you do svn status, you will see that a pom.xml has been created. Delete this. It is not required and just confuses users. + 1. If you do git status, you will see that a pom.xml (and it's associated signature) has been created. Delete this. It is not required and just confuses users. - 1. Tag it. - {{{svn copy https://svn.apache.org/repos/asf/nutch/trunk }}} {{{https://svn.apache.org/repos/asf/nutch/tags/release-X.Y-rcN -m "Nutch X.Y release." }}} + 1. Tag the release candidate. + {{{git tag -a release-X -m "Apache Nutch X RC#X Tag"}}} + 1. Push it to the remote host. + {{{git push origin release-X}}} 1. run the ant targets for '''zip-bin''', '''tar-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). The generated artifacts can be found in $NUTCH_HOME/dist. 1. Sign it all of the generated artifacts - [[http://www.apache.org/dev/release-signing.html|Step-By-Step Guide to Signing Releases]] ' - Consider using [[http://github.com/chrismattmann/apachestuff|Chris Mattmann's Apache Utility Scripts]]. 1. Check out the release management area at https://dist.apache.org/repos/dist/dev/nutch/{release.version} and copy all artifacts to here then commit this.
