[Hadoop Wiki] Update of "HowToRelease" by AndrewWang

[Apache Wiki]

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 AndrewWang:
https://wiki.apache.org/hadoop/HowToRelease?action=diff=95=96

  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. 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.)-- Recommend '''not''' closing, since it 
prevents JIRAs from being edited and makes it more difficult to track backports.
  
  = See Also =
   * [[http://www.apache.org/dev/release.html|Apache Releases FAQ]]

-
To unsubscribe, e-mail: common-commits-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-commits-h...@hadoop.apache.org

[Hadoop Wiki] Update of "HowToRelease" by AndrewWang

[Apache Wiki]

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 AndrewWang:
https://wiki.apache.org/hadoop/HowToRelease?action=diff=94=95

Comment:
More detailed instructions on how to bulk update JIRA versions

  
  = Preparation =
   1. If you have not already done so, 
[[http://www.apache.org/dev/release-signing.html#keys-policy|append your code 
signing key]] to the 
[[https://dist.apache.org/repos/dist/release/hadoop/common/KEYS|KEYS]] file. 
Once you commit your changes, they will automatically be propagated to the 
website. Also 
[[http://www.apache.org/dev/release-signing.html#keys-policy|upload your key to 
a public key server]] if you haven't. End users use the KEYS file (along with 
the [[http://www.apache.org/dev/release-signing.html#web-of-trust|web of 
trust]]) to validate that releases were done by an Apache committer. 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. Bulk update JIRA to unassign from this release all issues that are open 
non-blockers
+  1. Bulk update JIRA to unassign from this release all issues that are open 
non-blockers. This is involved since you can only bulk change issues within the 
same project, so minimally requires four bulk changes for each of HADOOP, HDFS, 
MAPREDUCE, and YARN. Editing the "Target Version/s" field is also a blind 
write, so you need to be careful not to lose any other fix versions that are 
set. For updating 3.0.0-beta1 to 3.0.0, the process looked like this:
+   1. Start with this query: 
+   {{{
+ project in (HADOOP, HDFS, YARN, MAPREDUCE) AND "Target Version/s" = 
3.0.0-beta1 and statusCategory != Done
+ }}}
+   1. Filter this list down until it's only issues with a Target Version of 
just "3.0.0-beta1". My query ended up looking like:
+   {{{
+ project in (HADOOP, HDFS, YARN, MAPREDUCE) AND "Target Version/s" = 
3.0.0-beta1 and "Target Versions/" not in (2.9.0, 2.8.3, 2.8.2) AND 
statusCategory != Done
+ }}}
+   1. Do the bulk update for each project individually to set the target 
version to 3.0.0.
+   1. Check the query for the next most common set of target versions and 
again filter it down:
+   {{{
+ project in (HADOOP, HDFS, YARN, MAPREDUCE) AND "Target Version/s" = 
3.0.0-beta1 and "Target Version/s" = 2.9.0 and statusCategory != Done
+ project in (HADOOP, HDFS, YARN, MAPREDUCE) AND "Target Version/s" = 
3.0.0-beta1 and "Target Version/s" = 2.9.0 and "Target Version/s" not in 
(2.8.2, 2.8.3) and statusCategory != Done
+ }}}
+   1. Do the bulk update for each project individually to set the target 
version field to (3.0.0, 2.9.0).
+   1. Return to the original query. If there aren't too many, update the 
remaining straggler issues by hand (faster than doing the bulk edits):
+   {{{
+ project in (HADOOP, HDFS, YARN, MAPREDUCE) AND "Target Version/s" = 
3.0.0-beta1 and statusCategory != Done
+ }}}
+ 
   1. Send follow-up notification to the developer list that this was done.
   1. To deploy artifacts to the Apache Maven repository create 
{{{~/.m2/settings.xml}}}:
   {{{

-
To unsubscribe, e-mail: common-commits-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-commits-h...@hadoop.apache.org

[Hadoop Wiki] Update of "HowToRelease" by AndrewWang

[Apache Wiki]

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 AndrewWang:
https://wiki.apache.org/hadoop/HowToRelease?action=diff=93=94

Comment:
Fix skipShade profile for deploy step

   1. Push branch-X.Y.Z and the newly created tag to the remote repo.
   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 deploy -Psign -DskipTests -DskipShading
+ mvn deploy -Psign -DskipTests -DskipShade
  }}}
   1. Copy release files to a public place and ensure they are readable. Note 
that {{{home.apache.org}}} only supports SFTP, so this may be easier with a 
graphical SFTP client like Nautilus, Konqueror, etc.
   {{{

-
To unsubscribe, e-mail: common-commits-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-commits-h...@hadoop.apache.org

[Hadoop Wiki] Update of "HowToRelease" by AndrewWang

[Apache Wiki]

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 AndrewWang:
https://wiki.apache.org/hadoop/HowToRelease?action=diff=92=93

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:
{{{
- 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}
  cd publish/docs
+ tar xvf /path/to/hadoop-${version}-site.tar.gz
  # Update current2, current, stable and stable2 as needed.
  # For example
  rm current2 current

-
To unsubscribe, e-mail: common-commits-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-commits-h...@hadoop.apache.org

[Hadoop Wiki] Update of "HowToRelease" by AndrewWang

[Apache Wiki]

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 AndrewWang:
https://wiki.apache.org/hadoop/HowToRelease?action=diff=91=92

   1. Push branch-X.Y.Z and the newly created tag to the remote repo.
   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 deploy -DskipTests
+ mvn deploy -Psign -DskipTests -DskipShading
  }}}
   1. Copy release files to a public place and ensure they are readable. Note 
that {{{home.apache.org}}} only supports SFTP, so this may be easier with a 
graphical SFTP client like Nautilus, Konqueror, etc.
   {{{

-
To unsubscribe, e-mail: common-commits-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-commits-h...@hadoop.apache.org

[Hadoop Wiki] Update of "HowToRelease" by AndrewWang

[Apache Wiki]

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 AndrewWang:
https://wiki.apache.org/hadoop/HowToRelease?action=diff=90=91

  }}}
   1. While it should fail {{{create-release}}} if there are issues, 
doublecheck the rat log to find and fix any potential licensing issues.
   {{{
-  grep 'Rat check' target/artifacts/mvn_apache_rat.log
+  grep 'Rat check' patchprocess/mvn_apache_rat.log
  }}}
   1. Check that release files look ok - e.g. install it somewhere fresh and 
run examples from tutorial, do a fresh build, read the release notes looking 
for WARNINGs, etc.
   1. Set environment variable version for later steps. {{{export 
version=X.Y.Z-RCN}}}

-
To unsubscribe, e-mail: common-commits-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-commits-h...@hadoop.apache.org

[Hadoop Wiki] Update of "HowToRelease" by AndrewWang

[Apache Wiki]

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 AndrewWang:
https://wiki.apache.org/hadoop/HowToRelease?action=diff=88=89

Comment:
Update website build instructions to point to HowToCommit instead

{{{
  svn add publish/docs/r${version}
  }}}
-   1. Regenerate the site, review it, then commit it.
+   1. Regenerate the site, review it, then commit it per the instructions in 
HowToCommit.
{{{
- 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.

-
To unsubscribe, e-mail: common-commits-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-commits-h...@hadoop.apache.org

[Hadoop Wiki] Update of "HowToRelease" by AndrewWang

[Apache Wiki]

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 AndrewWang:
https://wiki.apache.org/hadoop/HowToRelease?action=diff=86=87

Comment:
update instructions for uploading to home.apache.org

   {{{
  mvn deploy -DskipTests
  }}}
-  1. Copy release files to a public place and ensure they are readable.
+  1. Copy release files to a public place and ensure they are readable. Note 
that {{{home.apache.org}}} only supports SFTP, so this may be easier with a 
graphical SFTP client like Nautilus, Konqueror, etc.
   {{{
- ssh home.apache.org mkdir public_html/hadoop-${version}
- scp -p hadoop-${version}*.tar.gz* 
home.apache.org:public_html/hadoop-${version}
- ssh home.apache.org chmod -R a+r public_html/hadoop-${version}
+ sftp home.apache.org
+ > cd public_html
+ > mkdir hadoop-${version}
+ > put -r /home/hadoop/hadoop-${version}
+ 
+ > bye
  }}}
   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. 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/common-dev@hadoop.apache.org/msg13339.html|Example]]

-
To unsubscribe, e-mail: common-commits-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-commits-h...@hadoop.apache.org

[Hadoop Wiki] Update of "HowToRelease" by AndrewWang

[Apache Wiki]

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 AndrewWang:
https://wiki.apache.org/hadoop/HowToRelease?action=diff=80=81

Comment:
Remove manual CHANGES.txt related steps

  ## page was copied from HowToReleasePostMavenization
  ''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 2.5.1 and later releases to 
reflect the changes to version-control (git), build-scripts and mavenization.
+ These instructions have been updated for Hadoop 2.8.0 and later releases to 
reflect the changes to version-control (git), build-scripts and mavenization.
  
- Earlier versions of this document are at HowToReleaseWithSvnAndAnt and 
HowToReleasePostMavenization
+ Earlier versions of this document are at HowToReleaseWithSvnAndAnt and 
HowToReleasePostMavenization and HowToReleasePre2.8
  
  <>
  
@@ -32, +32 @@

  = Branching =
  When releasing Hadoop X.Y.Z, the following branching changes are required. 
Note that a release can match more than one of the following if-conditions. For 
a major release, one needs to make the changes for minor and point releases as 
well. Similarly, a new minor release is also a new point release.
  
-  1. Add the release X.Y.Z to CHANGES.txt files if it doesn't already exist 
(leave the date as unreleased for now). Commit these changes to any '''live''' 
upstream branch. For example, if you are handling 2.6.2, commit the changes to 
trunk, branch-2, branch-2.6, and branch-2.7 (provided branch-2.7 is an active 
branch).
-  {{{
- git commit -a -m "Adding release X.Y.Z to CHANGES.txt"
- }}}
   1. If this is a new major release (i.e., Y = 0 and Z = 0)
1. Create a new branch (branch-X) for all releases in this major release.
1. Update the version on trunk to (X+1).0.0-SNAPSHOT
@@ -100, +96 @@

  mvn apache-rat:check
  }}}
   1. Set environment variable version for later steps. {{{export 
version=X.Y.Z-RCN}}}
-  1. Set the release date for X.Y.Z to the current date in each CHANGES.txt 
file in branch-X.Y.Z and commit the changes.
-  {{{
- git commit -a -m "Set the release date for $version"
- }}}
   1. Tag the release candidate:
   {{{
  git tag -s release-$version -m "Release candidate - $version"
@@ -139, +131 @@

  = 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 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"
- }}}
   1. Tag the release. Do it from the release branch and push the created tag 
to the remote repository:
   {{{
  git tag -s rel/release-X.Y.Z -m "Hadoop X.Y.Z release"
  git push origin rel/release-X.Y.Z
  }}}
-  1. Use 
[[https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder|this Jenkins 
job]] to create the final release files
   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. 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 (it requires a PMC privilege)

[Hadoop Wiki] Update of HowToRelease by AndrewWang

[Apache Wiki]

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 AndrewWang:
https://wiki.apache.org/hadoop/HowToRelease?action=diffrev1=70rev2=71

Comment:
no more svn up for the website

  = 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, 
[[http://www.apache.org/dev/release-signing.html#keys-policy|append your code 
signing key]] to the 
[[https://dist.apache.org/repos/dist/release/hadoop/common/KEYS|KEYS]] file on 
the website. Also 
[[http://www.apache.org/dev/release-signing.html#keys-policy|upload your key to 
a public key server]] if you haven't. End users use the KEYS file (along with 
the [[http://www.apache.org/dev/release-signing.html#web-of-trust|web of 
trust]]) to validate that releases were done by an Apache committer. 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. If you have not already done so, 
[[http://www.apache.org/dev/release-signing.html#keys-policy|append your code 
signing key]] to the 
[[https://dist.apache.org/repos/dist/release/hadoop/common/KEYS|KEYS]] file. 
Once you commit your changes, they will automatically be propagated to the 
website. Also 
[[http://www.apache.org/dev/release-signing.html#keys-policy|upload your key to 
a public key server]] if you haven't. End users use the KEYS file (along with 
the [[http://www.apache.org/dev/release-signing.html#web-of-trust|web of 
trust]]) to validate that releases were done by an Apache committer. 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;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;

[Hadoop Wiki] Update of HowToRelease by AndrewWang

[Apache Wiki]

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 AndrewWang:
https://wiki.apache.org/hadoop/HowToRelease?action=diffrev1=69rev2=70

Comment:
update KEYS file instructions

  = 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, 
[[http://www.apache.org/dev/release-signing.html#keys-policy|append your code 
signing key]] to the 
[[https://dist.apache.org/repos/dist/release/hadoop/common/KEYS|KEYS]] file on 
the website. Also 
[[http://www.apache.org/dev/release-signing.html#keys-policy|upload your key to 
a public key server]] if you haven't. End users use the KEYS file (along with 
the [[http://www.apache.org/dev/release-signing.html#web-of-trust|web of 
trust]]) to validate that releases were done by an Apache committer. 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. If you have not already done so, update your @apache.org account via 
[[http://id.apache.org/|id.apache.org]] with your key; also 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;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;