You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-commits@hadoop.apache.org by Apache Wiki <wi...@apache.org> on 2009/08/03 15:19:49 UTC
[Hadoop Wiki] Update of "HowToRelease" by TomWhite
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.
The following page has been changed by TomWhite:
http://wiki.apache.org/hadoop/HowToRelease
The comment on the change is:
Update following project split (differences found while releasing 0.19.2)
------------------------------------------------------------------------------
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/core/trunk \
+ svn copy https://svn.apache.org/repos/asf/hadoop/common/trunk \
- https://svn.apache.org/repos/asf/hadoop/core/branches/branch-X.Y -m "Branching for X.Y releases"
+ https://svn.apache.org/repos/asf/hadoop/common/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.xml}}} on trunk to X.Y+1.0-dev.
@@ -34, +34 @@
These operations take place in the release branch.
1. Check out the branch with: {{{
- svn co https://svn.apache.org/repos/asf/hadoop/core/branches/branch-X.Y
+ svn co https://svn.apache.org/repos/asf/hadoop/common/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 {{{src/docs/releasenotes.html}}} with release notes for this release.
+ 1. Update {{{src/docs/releasenotes.html}}} with release notes for this release. You can get the HTML by following the "Release Notes" link for the relevant release on the [http://issues.apache.org/jira/browse/HADOOP?report=com.sourcelabs.jira.plugin.portlet.releases:releases-projecttab Releases] tab in Jira.
1. Update the version number in {{{build.xml}}} to be ''hadoop-X.Y.N-dev'', where ''N'' is one greater than the release being made.
1. Commit these changes. {{{
svn commit -m "Preparing for release X.Y.Z"
@@ -47, +47 @@
svn merge -rR1:R2 ../trunk .
svn commit -m "Merge -r R1:R2 from trunk to X.Y branch. Fixes: HADOOP-A, HADOOP-B."
}}}
- 1. Tag the release candidate (R is the release candidate number): {{{
+ 1. Tag the release candidate (R is the release candidate number, and starts from 0): {{{
- svn copy https://svn.apache.org/repos/asf/hadoop/core/branches/branch-X.Y \
+ svn copy https://svn.apache.org/repos/asf/hadoop/common/branches/branch-X.Y \
- https://svn.apache.org/repos/asf/hadoop/core/tags/release-X.Y.Z-rcR -m "Hadoop X.Y.Z-rcR release."
+ https://svn.apache.org/repos/asf/hadoop/common/tags/release-X.Y.Z-rcR -m "Hadoop X.Y.Z-rcR release."
}}}
@@ -57, +57 @@
To build an official release, you must:
- 1. Use a 64-bit Linux system, so that we can [http://hadoop.apache.org/core/docs/current/native_libraries.html build native code] for both 32- and 64-bit architectures.
+ 1. Use a 64-bit Linux system, so that we can [http://hadoop.apache.org/common/docs/current/native_libraries.html build native code] for both 32- and 64-bit architectures.
1. Have a recent version of [http://www.eclipse.org/ Eclipse] installed, so that the eclipse plugin will build.
@@ -86, +86 @@
ssh people.apache.org mkdir public_html/hadoop-X.Y.Z-candidate-0
scp -p hadoop-X.Y.Z.tar.gz* people.apache.org:public_html/hadoop-X.Y.Z-candidate-0
}}}
- 1. Call a release vote on core-dev at hadoop.apache.org.
+ 1. Call a release vote on common-dev at hadoop.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/core/tags/release-X.Y.Z-rcR \
+ svn move https://svn.apache.org/repos/asf/hadoop/common/tags/release-X.Y.Z-rcR \
- https://svn.apache.org/repos/asf/hadoop/core/tags/release-X.Y.Z -m "Hadoop X.Y.Z release."
+ https://svn.apache.org/repos/asf/hadoop/common/tags/release-X.Y.Z -m "Hadoop X.Y.Z release."
}}}
1. Copy release files to the distribution directory and make them writable by the hadoop group. {{{
ssh people.apache.org
@@ -110, +110 @@
}}}
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/core/site
+ svn co https://svn.apache.org/repos/asf/hadoop/common/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}}}.
@@ -121, +121 @@
}}}
1. Deploy your site changes. {{{
ssh people.apache.org
- cd /www/hadoop.apache.org/core
+ cd /www/hadoop.apache.org/common
svn up
}}}
- 1. Copy the new release docs to {{{people.apache.org:/www/hadoop.apache.org/core/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/hadoop.apache.org/common/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/core/hadoop-X.Y.Z/hadoop-X.Y.Z.tar.gz '*/docs'
chmod -R 775 hadoop-X.Y.Z
chgrp -R hadoop hadoop-X.Y.Z
- cp -rp hadoop-X.Y.Z/docs /www/hadoop.apache.org/core/docs/rX.Y.Z
+ cp -rp hadoop-X.Y.Z/docs /www/hadoop.apache.org/common/docs/rX.Y.Z
rm -r hadoop-X.Y.Z
- cd /www/hadoop.apache.org/core/docs/
+ cd /www/hadoop.apache.org/common/docs/
ln -s rX.Y.Z current
}}}
1. Generate the jdiff API data for the new release by, in the branch directory, running {{{