Dear Wiki user,

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

The "Hive/HowToRelease" page has been changed by CarlSteinbach.
http://wiki.apache.org/hadoop/Hive/HowToRelease?action=diff&rev1=18&rev2=19

--------------------------------------------------

  
  Skip this section if this is NOT the first release in a series (i.e. release 
X.Y.0).
  
-       1. Notify developers on the ##hive IRC channel that you are about to 
branch a release. 
+       1. Notify developers on the #hive 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"
@@ -21, +21 @@

  https://svn.apache.org/repos/asf/hive/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.properties}}} on trunk to 
X.Y+1.0.
+         1. Increment the value of the {{{version}}} property the 
{{{build.properties}}} file on trunk. For example, if the current value is 
{{{0.7.0-SNAPSHOT}}}, the new value should be {{{0.8.0-SNAPSHOT}}}. Please note 
that the {{{SNAPSHOT}}} suffix is required in order to indicate that this is an 
unreleased development branch.
        1. Commit these changes to trunk. {{{
  svn commit -m "Preparing for X.Y+1.0 development"
  }}}
@@ -30, +30 @@

  
  These operations take place in the release branch.
  
-       1. Check out the branch with: {{{
+       1. Check out the release branch with: {{{
  svn co https://svn.apache.org/repos/asf/hive/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 the version number in {{{build.properties}}} to be 
''hive-X.Y.Z'' where Z is the point release number in this release series (0 
for the first one, in which case this step is a no-op since you already did 
this above when creating the branch).
+       1. Update the {{{version}}} property value in the 
{{{build.properties}}} file. You should remove the {{{SNAPSHOT}}} suffix and 
set {{{version}}} equal to {{{hive-X.Y.Z}}} where Z is the point release number 
in this release series (0 for the first one, in which case this step is a no-op 
since you already did this above when creating the branch).
        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.   We don't currently use svn 
merge for this, but if we did, the script would be {{{
+       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. We don't currently use svn merge 
for this, but if we did, the script would be {{{
  cd branch-X.Y
  svn merge -rR1:R2 ../trunk .
  svn commit -m "Merge -r R1:R2 from trunk to X.Y branch. Fixes: HIVE-A, 
HIVE-B."
@@ -121, +121 @@

  ln -s rX.Y.Z current
  }}}
        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 
Hive'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 
Hive'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 =
  

Reply via email to