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 2014/11/21 05:00:12 UTC

[Hadoop Wiki] Update of "HowToReleasePostMavenizationWithGit" by karthikkambatla

Dear Wiki user,

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

The "HowToReleasePostMavenizationWithGit" page has been changed by karthikkambatla:
https://wiki.apache.org/hadoop/HowToReleasePostMavenizationWithGit?action=diff&rev1=64&rev2=65

  = 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 of 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"}}}
-         1. Tag the release: {{{
+   1. Tag the release: {{{
  git tag -s release-X.Y.Z -m "Hadoop X.Y.Z release"}}}
+   1. Copy release files to the distribution directory
+      1. Check out the corresponding svn repo if need be {{{
+ svn co https://dist.apache.org/repos/dist/release/hadoop/common/ hadoop-dist
- 	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-${version}-candidate-0 /www/www.apache.org/dist/hadoop/core/hadoop-${version}
- cd /www/www.apache.org/dist/hadoop/core
- chgrp -R hadoop hadoop-${version}
- chmod -R g+w hadoop-${version}
  }}}
+      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 {{{
+ svn ci -m "Publishing the bits for release ${version}"
- 	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-${version}; rm stable
- ln -s hadoop-${version} stable
  }}}
- 	1. In [[https://repository.apache.org|Nexus]], effect the release of artifacts by right-clicking the staged repository and select {{{Release}}}
+   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. Wait 24 hours for release to propagate to mirrors.
-         1. Prepare to edit the website. {{{
+   1. Edit the website.
+      1. Checkout the website if you haven't already {{{
- svn co  https://svn.apache.org/repos/asf/hadoop/common/site/main
+ svn co https://svn.apache.org/repos/asf/hadoop/common/site/main hadoop-common-site
  }}}
- 	1. Update the documentation links in {{{author/src/documentation/content/xdocs/site.xml}}}.
+      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. Update the release news in {{{author/src/documentation/content/xdocs/releases.xml}}}.
+      1. Update the news on the home page {{{author/src/documentation/content/xdocs/index.xml}}}.
-         1. Copy the new release docs to svn and update the {{{docs/current}}} link, by doing the following: {{{
+      1. Copy the new release docs to svn and update the {{{docs/current}}} link, by doing the following: {{{
  tar xvf /www/www.apache.org/dist/hadoop/core/hadoop-${version}/hadoop-${version}.tar.gz 
  cp -rp hadoop-${version}/share/doc/hadoop publish/docs/r${version}
  rm -r hadoop-${version}
- rm current
+ rm current2 current
- ln -s r${version} current
+ ln -s r${version} current2
+ ln -s current2 current
+ }}}
+      1. Similarly update the symlinks for stable if need be.
+      1. Add the documentation changes. {{{
  svn add publish/docs/r${version}
  }}}
- 	1. Regenerate the site, review it, then commit it. {{{
+      1. Regenerate the site, review it, then commit it. {{{
- ant -Dforrest.home=/usr/local/forrest -Djava5.home=/usr/local/jdk1.5
+ ant -Dforrest.home=$FORREST_HOME -Djava5.home=/usr/local/jdk1.5
  firefox publish/index.html
  svn commit -m "Updated site for release X.Y.Z."
  }}}
- 	1. Send announcements to the user and developer lists once the site changes are visible.
+   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, 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, "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.
+   1. In Jira, close issues resolved in the release.  Disable mail notifications for this bulk change.
  
  = See Also =