You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by Apache Wiki <wi...@apache.org> on 2017/11/13 08:27:02 UTC
[Nutch Wiki] Update of "Release_HOWTO" by SebastianNagel
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 SebastianNagel:
https://wiki.apache.org/nutch/Release_HOWTO?action=diff&rev1=55&rev2=56
Comment:
Should build the release packages from a clean checkout
= Prepping the Release Candidate =
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. From now on, use the branch created above.
+ 1. Create a branch branch-x.x, from now on, use the branch created above.
1. Update version numbers (from X.Y-SNAPSHOT to X.Y) for release in:
* conf/nutch-default.xml - http.agent.version property
* default.properties - version property and year property
@@ -17, +17 @@
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 to the branch you are releasing.
- 1. Make a clean checkout.
+ 1. To avoid that "forgotten" files in your development environment are packaged, make a '''clean''' checkout for the release branch or tag:
+ {{{cd ...}}}
+ {{{git clone https://github.com/apache/nutch.git branch-x.x}}}
+ {{{cd branch-x.x}}}
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.