You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nutch.apache.org by Apache Wiki <wi...@apache.org> on 2005/09/01 21:14:02 UTC

[Nutch Wiki] Update of "Release HOWTO" by PiotrKosiorowski

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 tag and branch names as propsed by Doug

------------------------------------------------------------------------------
  		 {{{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/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}}}.
  	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).
@@ -32, +32 @@

  = 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/lucene/nutch/tags/release-X.Y \}}}
-                 {{{ https://svn.apache.org/repos/asf/lucene/nutch/branches/Release-X.Y \}}}
+                 {{{ https://svn.apache.org/repos/asf/lucene/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: