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=22&rev2=23

  <<TableOfContents(3)>>
  
  = 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" }}}
          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.
  
  = Prepping the Release Candidate =
+         1. From now on, use the branch created above.
        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. 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/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/nutch/trunk/}}}.
        1. Build it.
                 {{{ant tar}}}
        1. Run unit tests.
@@ -29, +30 @@

          1. Once you've read, and are happy with the staging repos, close it.
          1. Remove the maven-ant-tasks jar from the ivy directory 
        1. Tag it. 
-               {{{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." }}}  
+               {{{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." }}}  
        1. run '''tar-bin''', '''tar-src''', '''zip-bin''', '''zip-src''' (if 
releasing trunk) and the first two if releasing 2.X (this is because 2.x is 
only released as source.).
          1. Sign it all of the generated artifacts - 
[[http://www.apache.org/dev/release-signing.html|Step-By-Step Guide to Signing 
Releases]] '''N.B.''' an md5, sha and asc should accompany each release 
artifact.
          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)

Reply via email to