hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Hadoop Wiki] Update of "Hive/HowToRelease" by JohnSichi
Date Tue, 26 Oct 2010 22:44:49 GMT
Dear Wiki user,

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

The "Hive/HowToRelease" page has been changed by JohnSichi.
http://wiki.apache.org/hadoop/Hive/HowToRelease?action=diff&rev1=15&rev2=16

--------------------------------------------------

  svn commit -m "Preparing for release X.Y.Z"
  }}}
  	1. Create a branch for the release series: {{{
- svn copy https://svn.apache.org/repos/asf/hadoop/hive/trunk \
+ svn copy https://svn.apache.org/repos/asf/hive/trunk \
- https://svn.apache.org/repos/asf/hadoop/hive/branches/branch-X.Y -m "Branching for X.Y releases"
+ https://svn.apache.org/repos/asf/hive/branches/branch-X.Y -m "Branching for X.Y releases"
  }}}
  	1. Update {{{CHANGES.txt}}} to add back in {{{Trunk (unreleased changes)}}}.
          1. Update the default version in {{{build.properties}}} on trunk to X.Y+1.0.
@@ -31, +31 @@

  These operations take place in the release branch.
  
  	1. Check out the branch with: {{{
- svn co https://svn.apache.org/repos/asf/hadoop/hive/branches/branch-X.Y
+ svn co https://svn.apache.org/repos/asf/hive/branches/branch-X.Y
  }}}
  	1. Update {{{CHANGES.txt}}} to include the release version and date (this change must be
committed to trunk and any intermediate branches between trunk and the branch being released).
  	1. Update the version number in {{{build.properties}}} to be ''hive-X.Y.Z'' where Z is
the point release number in this release series (0 for the first one, in which case this step
is a no-op since you already did this above when creating the branch).
@@ -46, +46 @@

  	1. You probably also want to commit a patch (on both trunk and branch) which updates README.txt
to bring it up to date (at a minimum, search+replacing references to the  version number).
 Also check NOTICE to see if anything needs to be updated for recent library dependency changes
or additions.
          1. Likewise, use JIRA's [[https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12310843|Release
Notes]] link to generate content for the RELEASE_NOTES.txt file. Be sure to select 'Text'
format.  (It's OK to do this with a direct commit rather than a patch.)
  	1. Tag the release candidate (R is the release candidate number, and also starts from 0):
{{{
- svn copy https://svn.apache.org/repos/asf/hadoop/hive/branches/branch-X.Y \
+ svn copy https://svn.apache.org/repos/asf/hive/branches/branch-X.Y \
- https://svn.apache.org/repos/asf/hadoop/hive/tags/release-X.Y.Z-rcR -m "Hive X.Y.Z-rcR release."
+ https://svn.apache.org/repos/asf/hive/tags/release-X.Y.Z-rcR -m "Hive X.Y.Z-rcR release."
  }}}
  
  
@@ -72, +72 @@

  ssh people.apache.org mkdir public_html/hive-X.Y.Z-candidate-0
  scp -p hive-X.Y.Z*.tar.gz* people.apache.org:public_html/hive-X.Y.Z-candidate-0
  }}}
-         1. Call a release vote on hive-dev at hadoop.apache.org.
+         1. Call a release vote on dev at hive.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. Tag the release: {{{
- svn move https://svn.apache.org/repos/asf/hadoop/hive/tags/release-X.Y.Z-rcR \
+ svn move https://svn.apache.org/repos/asf/hive/tags/release-X.Y.Z-rcR \
- https://svn.apache.org/repos/asf/hadoop/hive/tags/release-X.Y.Z -m "HiveX.Y.Z release."
+ https://svn.apache.org/repos/asf/hive/tags/release-X.Y.Z -m "HiveX.Y.Z release."
  }}}
- 	1. Copy release files to the distribution directory and make them writable by the hadoop
group. {{{
+ 	1. Copy release files to the distribution directory and make them writable by the hive
group. {{{
  ssh people.apache.org
- cp -pr public_html/hive-X.Y.Z-candidate-0 /www/www.apache.org/dist/hadoop/hive/hive-X.Y.Z
+ cp -pr public_html/hive-X.Y.Z-candidate-0 /www/www.apache.org/dist/hive/hive-X.Y.Z
- cd /www/www.apache.org/dist/hadoop/hive
+ cd /www/www.apache.org/dist/hive
- chgrp -R hadoop hive-X.Y.Z
+ chgrp -R hive hive-X.Y.Z
  chmod -R g+w hive-X.Y.Z
  }}}
  	1. The release directory usually contains just two releases, the most recent from two branches,
with a link named 'stable' to the most recent recommended version. {{{
  ssh people.apache.org
- cd /www/www.apache.org/dist/hadoop/hive
+ cd /www/www.apache.org/dist/hive
  rm -rf hive-A.B.C; rm stable
  ln -s hive-A.B.D stable
  }}}
  	1. Wait 24 hours for release to propagate to mirrors.
          1. Prepare to edit the website. {{{
- svn co https://svn.apache.org/repos/asf/hadoop/hive/site
+ svn co https://svn.apache.org/repos/asf/hive/site
  }}}
  	1. Update the documentation links in {{{author/src/documentation/content/xdocs/site.xml}}}.
  	1. Update the release news in {{{author/src/documentation/content/xdocs/releases.xml}}}.
@@ -107, +107 @@

  }}}
  	1. Deploy your site changes. {{{
  ssh people.apache.org
- cd /www/hadoop.apache.org/hive
+ cd /www/hive.apache.org
  svn up
  }}}
- 	1. Copy the new release docs to {{{people.apache.org:/www/hadoop.apache.org/hive/docs/rX.Y.Z}}}
and update the {{{docs/current}}} link, by doing the following in your home directory on people.apache.org:
{{{
+ 	1. Copy the new release docs to {{{people.apache.org:/www/hive.apache.org/docs/rX.Y.Z}}}
and update the {{{docs/current}}} link, by doing the following in your home directory on people.apache.org:
{{{
  ssh people.apache.org
- tar xvf /www/www.apache.org/dist/hadoop/hive/hive-X.Y.Z/hive-X.Y.Z.tar.gz '*/docs'
+ tar xvf /www/www.apache.org/dist/hive/hive-X.Y.Z/hive-X.Y.Z.tar.gz '*/docs'
  chmod -R ug=rwX,o=rX hive-X.Y.Z
- chgrp -R hadoop hive-X.Y.Z
+ chgrp -R hive hive-X.Y.Z
- cp -rp hive-X.Y.Z/docs /www/hadoop.apache.org/hive/docs/rX.Y.Z
+ cp -rp hive-X.Y.Z/docs /www/hive.apache.org/docs/rX.Y.Z
  rm -r hive-X.Y.Z
- cd /www/hadoop.apache.org/hive/docs/
+ cd /www/hive.apache.org/docs/
  ln -s rX.Y.Z current
  }}}
          1. Generate the jdiff API data for the new release by, in the branch directory,
running {{{

Mime
View raw message