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 DougCutting
Date Tue, 08 May 2007 22:04:43 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 DougCutting:
http://wiki.apache.org/lucene-hadoop/HowToRelease

------------------------------------------------------------------------------
  ''This page is prepared for Hadoop committers. You need committer rights 
  to create a new  Hadoop release.''
  
- = Making a release. =
+ = Preparation =
  
  	1. Check if documentation needs an update.
                  {{{cd src/docs; forrest; cp -pr build/site/* ../../docs}}}
@@ -12, +12 @@

  	1. Update ''CHANGES.txt'' to include the release version and date.
  	1. Commit these changes.
  		{{{svn commit -m "Preparing for release X.Y.Z"}}}
+ 
+ = Branching & Merging =
+ 
  	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. You can find the revision numbers using
{{{svn log CHANGES.txt}}} in the branch and in trunk.
+ 	1. Merge desired patches from 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 -m "Merge -r R1:R2 from trunk to X.Y branch. Fixes: HADOOP-A,
HADOOP-B."}}}
+ = Building =
+ 
  	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.
@@ -27, +32 @@

                  {{{md5sum hadoop-X.Y.Z.tar.gz > hadoop-X.Y.Z.tar.gz.md5}}}
  	1. Sign the release (see [http://www.apache.org/dev/mirror-step-by-step.html?Step-By-Step
Step-By-Step Guide to Mirroring Releases] for more information).
                  {{{gpg --armor --output hadoop-X.Y.Z.tar.gz.asc --detach-sig hadoop-X.Y.Z.tar.gz}}}
+ 	1. Copy release files to a public place.
+                 {{{ssh people.apache.org mkdir public_html/hadoop-X.Y.Z}}}
+                 {{{scp -p hadoop-X.Y.Z.tar.gz* people.apache.org:public_html/hadoop-X.Y.Z}}}
+         1. Call a release vote on hadoop-dev at lucene.apache.org.
+ 
+ = Publishing =
+ Once [http://www.apache.org/foundation/voting.html#ReleaseVotes three PMC members have voted
for a release], it may be published.
  	1. Copy release files to the distribution directory.
                  {{{ssh people.apache.org mkdir /www/www.apache.org/dist/lucene/hadoop/hadoop-X.Y.Z}}}
                  {{{scp -p hadoop-X.Y.Z.tar.gz* people.apache.org:/www/www.apache.org/dist/lucene/hadoop/hadoop-X.Y.Z}}}
@@ -48, +60 @@

  	1. Send announcements to the user and developer lists.
          1. In Jira, close issues resolved in the release.  (You need to be in the ''hadoop-admin''
group to do this.) Disable mail notifications for this bulk change.
  
+ = See Also =
+ 
+  * [http://www.apache.org/dev/release.html Apache Releases FAQ]
+ 

Mime
View raw message