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 "HowToReleasePostMavenization" by Arun C Murthy
Date Tue, 01 Nov 2011 05:34:01 GMT
Dear Wiki user,

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

The "HowToReleasePostMavenization" page has been changed by Arun C Murthy:

New page:
''This page is prepared for Hadoop Core committers. You need committer rights 
to create a new  Hadoop Core release.''

These instructions have been updated for Hadoop 0.20.0 and later releases.  For earlier releases,
check out an [[http://wiki.apache.org/hadoop/HowToRelease?action=recall&rev=48|older revision]]
of this page. For 0.21.0 and later many of the steps need to be done in turn for Common, HDFS,
and MapReduce.

= Preparation =

        1. Bulk update Jira to unassign from this release all issues that are open non-blockers
and send follow-up notification to the developer list that this was done.
	1. If you have not already done so, add and commit your public key to the Hadoop repository
[[http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS|KEYS]], appending the output of
the following commands:{{{
gpg --armor --fingerprint --list-sigs <keyid>
gpg --armor --export <keyid>
}}} and publish your key at [[http://pgp.mit.edu/]]. Once you commit your changes, log into
{{{people.apache.org}}} and pull updates to {{{/www/www.apache.org/dist/hadoop/core}}}. For
more details on signing releases, see [[http://www.apache.org/dev/release-signing.html|Signing
Releases]] and [[http://www.apache.org/dev/mirror-step-by-step.html?Step-By-Step|Step-By-Step
Guide to Mirroring Releases]].
	1. To deploy artifacts to the Apache Maven repository create {{{~/.m2/settings.xml}}}:{{{
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
     <username>Apache username</username>
     <password>Apache password</password>

= Branching =

Skip this section if this is NOT the first release in a series (i.e. release X.Y.0).

	1. Notify developers on the #hadoop IRC channel that you are about to branch a release. 
	1. Update {{{CHANGES.txt}}} to include the release version and date (use {{{Unreleased}}}
for the date if it is unknown) and remove {{{Trunk (unreleased changes)}}}.
	1. Commit these changes to trunk. {{{
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/common/trunk \
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.
	1. Update the version number in {{{src/docs/src/documentation/content/xdocs/tabs.xml}}} on
trunk to X.Y+1.0.
        1. Update the {{{project.version}}} number in {{{/src/test/aop/build/aop.xml}}} on
trunk to X.Y+1.0.
        1. Update the {{{hadoop-*.version}}} numbers in {{{ivy/libraries.properties}}} on
trunk to X.Y+1.0.
	1. Commit these changes to trunk. {{{
svn commit -m "Preparing for X.Y+1.0 development"

= Updating Release Branch =

These operations take place in the release branch.

	1. Check out the branch with: {{{
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. You generate
these with: {{{
cd src/docs
jira.sh -s https://issues.apache.org/jira -u $user -p $pw \
   -a getIssueList --search \
   "project in (HADOOP,HDFS,MAPREDUCE) and fixVersion = '$vers' and resolution = Fixed" \
   | ./relnotes.py > $vers.html
}}} edit the releasenotes.html with the list of items from $vers.html. 
	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"
	1. If not already done, 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."
	1. Tag the release candidate (R is the release candidate number, and starts from 0): {{{
svn copy https://svn.apache.org/repos/asf/hadoop/common/branches/branch-X.Y \
https://svn.apache.org/repos/asf/hadoop/common/tags/release-X.Y.Z-rcR -m "Hadoop X.Y.Z-rcR

= Build Requirements =

To build an official release, you must:

  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.

  1. Have [[http://xerces.apache.org/xerces-c/download.cgi|Xerces C]] 2.8.x installed.

[[https://issues.apache.org/jira/browse/HADOOP-6846|HADOOP-6846]] has some scripts that make
it easier to build and smoke test a release for 0.21.0 and later.

= Building =

	1. Build the release & run unit tests.  This is captured in [[http://svn.apache.org/viewvc/hadoop/nightly/hudsonBuildHadoopRelease.sh?view=markup]].
	1. Check that release file looks ok - e.g. install it and run examples from tutorial.
        1. Generate the checksums of the release file. {{{
gpg --print-mds hadoop-X.Y.Z.tar.gz > hadoop-X.Y.Z.tar.gz.mds
	1. Sign the release {{{
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-candidate-0
scp -p hadoop-X.Y.Z.tar.gz* people.apache.org:public_html/hadoop-X.Y.Z-candidate-0
	1. Stage the release candidate to the maven repository: {{{
ant -Dversion=X.Y.Z -Drepo=staging mvn-deploy
	1. Log into [[https://repository.apache.org|Nexus]], select {{{Staging}}} from the left navigation
pane, right-click on the pushed repository, and {{{close}}} the release.
        1. Call a release vote on common-dev at hadoop.apache.org.

= Publishing =

In 7 days if [[http://hadoop.apache.org/bylaws#Decision+Making|the release vote passes]],
the release may be published.
	1. Tag the release: {{{
svn move https://svn.apache.org/repos/asf/hadoop/common/tags/release-X.Y.Z-rcR \
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
cp -pr public_html/hadoop-X.Y.Z-candidate-0 /www/www.apache.org/dist/hadoop/core/hadoop-X.Y.Z
cd /www/www.apache.org/dist/hadoop/core
chgrp -R hadoop hadoop-X.Y.Z
chmod -R g+w hadoop-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/core
rm -rf hadoop-A.B.C; rm stable
ln -s hadoop-A.B.D stable
	1. In [[https://repository.apache.org|Nexus]], effect the release of artifacts by right-clicking
the staged repository and select {{{Release}}}
	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/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}}}.
	1. Regenerate the site, review it, then commit it. {{{
ant -Dforrest.home=/usr/local/forrest -Djava5.home=/usr/local/jdk1.5
firefox publish/index.html
svn commit -m "Updated site for release X.Y.Z."
	1. Deploy your site changes. {{{
ssh people.apache.org
cd /www/hadoop.apache.org/common
svn up
	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 ug=rwX,o=rX hadoop-X.Y.Z
chgrp -R hadoop hadoop-X.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/common/docs/
ln -s rX.Y.Z current
        1. Generate the jdiff API data for the new release by, in the branch directory, running
ant -Dversion=X.Y.Z api-xml
}}} then commit the new XML file generated in lib/jdiff to both trunk and to the branch (and
any intermediate branches between trunk and the branch being released). {{{
svn commit -m "JDiff output for release X.Y.Z"

	1. Update the {{{jdiff.stable}}} value in the X.Y+1 branch's {{{build.xml}}} (which may be
trunk) to be the published release (ie. X.Y.Z).
	1. Send announcements to the user and developer lists once the site changes are visible.
        1. In Jira, ensure that only issues in the "Fixed" state have a "Fix Version" set
to release X.Y.Z.
        1. In Jira, "release" the version.  Visit the "Administer Project" page, then the
"Manage versions" page.   You need to have the "Admin" role in Hadoop Core's Jira for this
step and the next.
        1. In Jira, close issues resolved in the release.  Disable mail notifications for
this bulk change.

= See Also =

 * [[http://www.apache.org/dev/release.html|Apache Releases FAQ]]

View raw message