hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Lucene-hadoop Wiki] Update of "HowToRelease" by TomWhite
Date Sat, 17 Mar 2007 23:22:10 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucene-hadoop Wiki" for change notification.

The following page has been changed by TomWhite:
http://wiki.apache.org/lucene-hadoop/HowToRelease

The comment on the change is:
Minor fixes.

------------------------------------------------------------------------------
  
  	1. Check if documentation needs an update.
                  {{{cd src/docs; forrest; cp -pr build/site/* ../../docs}}}
- 	1. Update news in ''src/site/src/documentation/content/xdocs/index.xml''.
+ 	1. Update news in ''src/docs/src/documentation/content/xdocs/index.xml''. Then regenerate
the documentation.
  	1. Update version number in ''build.xml'' to be ''hadoop-X.Y.N-dev'', where ''N'' is one
greater than the release being made.
  	1. Update ''CHANGES.txt'' to include the release version and date.
  	1. Commit these changes.
@@ -15, +15 @@

  	1. If this is the first release in a series (i.e. release X.Y.0), then create a branch
for the series:
   		{{{svn copy https://svn.apache.org/repos/asf/lucene/hadoop/trunk \}}} 			{{{https://svn.apache.org/repos/asf/lucene/hadoop/branches/branch-X.Y
-m "Branching for X.Y releases" }}}
  	1. Check out the branch with: 		{{{svn co https://svn.apache.org/repos/asf/lucene/hadoop/branches/branch-X.Y}}}
- 	1. If the branch for the series already existed (i.e. release X.Y.Z where Z > 0), then
merge trunk into the branch and commit these changes.
+ 	1. If the branch for the series already existed (i.e. release X.Y.Z where Z > 0), then
merge trunk into the branch and commit these changes. You can find the revision numbers using
{{{svn log CHANGES.txt}}} in the branch and in trunk.
-  		{{{cd branch-X.Y; svn merge -rR1:R2 ../trunk .; svn commit}}}
+  		{{{cd branch-X.Y; svn merge -rR1:R2 ../trunk .;}}}
+                 {{{svn commit -m "Merge -r R1:R2 from trunk to X.Y branch. Fixes: HADOOP-A,
HADOOP-B."}}}
  	1. Build the release & run unit tests.  Note that releases are normally built on 32-bit
Linux, so that they include the native code for that platform.
  		 {{{ant -Dversion=X.Y.Z -Dcompile.native=true clean tar test}}}
  	1. Check that release file looks ok - e.g. install it and run examples from tutorial.
@@ -35, +36 @@

  	1. Wait 24 hours for release to propagate to mirrors.
  	1. Deploy new Hadoop site.
                  {{{ssh people.apache.org; cd /www/lucene.apache.org/hadoop; svn up}}}
- 	1. Update Javadoc in {{{people.apache.org:/www/lucene.apache.org/hadoop/docs/api}}}.
+ 	1. Update Javadoc in {{{people.apache.org:/www/lucene.apache.org/hadoop/api}}}.
  	1. Send announcements to the user and developer lists.
          1. In Jira, close issues resolved in the release.  Disable mail notifications for
this bulk change.
  

Mime
View raw message