Dear Wiki user, You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.
The "HowToRelease" page has been changed by SangjinLee: https://wiki.apache.org/hadoop/HowToRelease?action=diff&rev1=76&rev2=77 Comment: updated the how-to-release document based on the 2.6.2 experience git commit -a -m "Preparing for X.Y.(Z+1) development" }}} 1. Release branch (branch-X.Y.Z) updates: - 1. Update {{{hadoop-project//src/site/markdown/index.md.vm}}} to reflect the right versions, new features and big improvements. + 1. Update {{{hadoop-project/src/site/markdown/index.md.vm}}} to reflect the right versions, new features and big improvements. 1. Update the version on branch-X.Y.Z TO X.Y.Z {{{ mvn versions:set -DnewVersion=X.Y.Z @@ -109, +109 @@ git tag -s release-$version -m "Release candidate - $version" }}} 1. Push branch-X.Y.Z and the newly created tag to the remote repo. - 1. Deploy the maven artifacts, on your personal computer. (You might want to do this in private and clear your history file as your gpg-passphrase is in clear text) + 1. Deploy the maven artifacts, on your personal computer. Please be sure you have completed the prerequisite step of preparing the {{{settings.xml}}} file before the deployment. You might want to do this in private and clear your history file as your gpg-passphrase is in clear text. {{{ mvn clean deploy -Psign,src,dist -DskipTests -Dgpg.passphrase=<your-gpg-passphrase> }}} @@ -120, +120 @@ gpg --print-mds hadoop-${version}-src.tar.gz > hadoop-${version}-src.tar.gz.mds gpg --print-mds hadoop-${version}.tar.gz > hadoop-${version}.tar.gz.mds }}} - 1. Sign the release + 1. Sign the release. Please be sure you have completed the prerequisite step of preparing the key before signing. {{{ gpg --armor --output hadoop-${version}-src.tar.gz.asc --detach-sig hadoop-${version}-src.tar.gz gpg --armor --output hadoop-${version}.tar.gz.asc --detach-sig hadoop-${version}.tar.gz }}} - 1. Copy release files to a public place. + 1. Copy release files to a public place and ensure they are readable. {{{ ssh people.apache.org mkdir public_html/hadoop-${version} scp -p hadoop-${version}.tar.gz* people.apache.org:public_html/hadoop-${version} + ssh people apache.org chmod -R a+r public_html/hadoop-${version} }}} 1. Log into [[https://repository.apache.org|Nexus]], select "{{{Staging}}} Repositories" from the left navigation pane, select the check-box against the specific hadoop repository, and {{{close}}} the release. - 1. Call a release vote on common-dev at hadoop.apache.org. [[https://www.mail-archive.com/[email protected]/msg13339.html|Example]] + 1. Call a release vote on common-dev at hadoop.apache.org. It's usually a good idea to start the release vote on Monday so that people will have a chance to verify the release candidate during the week. [[https://www.mail-archive.com/[email protected]/msg13339.html|Example]] + 1. If the release candidate contains a serious issue, withdraw the vote, make necessary changes, and repeat this process. + 1. If non-trivial changes are committed to the release branch, ensure the commits are present in the upstream branches. = Publishing = In 5 days if [[http://hadoop.apache.org/bylaws#Decision+Making|the release vote passes]], the release may be published. - 1. Update the release date in CHANGES.txt of trunk, branch-X, branch-X.Y to reflect the one in branch-X.Y.Z. Commit and push those changes. + 1. Update the release date in CHANGES.txt to the final release vote passage date, and commit them to all live upstream branches (e.g., trunk, branch-X, branch-X.Y) to reflect the one in branch-X.Y.Z. Commit and push those changes. {{{ git commit -a -m "Set the release date for X.Y.Z" }}} @@ -152, +155 @@ 1. Generate new .mds files referring to the final release tarballs and not the RCs 1. Copy the release files to hadoop-dist/hadoop-${version} 1. Update the symlinks to current2 and stable2. The release directory usually contains just two releases, the most recent from two branches. - 1. Commit the changes + 1. Commit the changes (it requires a PMC privilege) {{{ svn ci -m "Publishing the bits for release ${version}" }}}
