pig-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Pig Wiki] Update of "HowToRelease" by AlanGates
Date Wed, 06 Oct 2010 23:41:33 GMT
Dear Wiki user,

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

The "HowToRelease" page has been changed by AlanGates.
http://wiki.apache.org/pig/HowToRelease?action=diff&rev1=22&rev2=23

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

- This page is to document the release procedure for Pig. Pig is a fairly young Apache project.
Its release process is work in progress and is modeled from [[http://wiki.apache.org/pig/HowToRelease|Hadoop
Release Procedure]].
+ This page is to document the release procedure for Pig. Pig is a fairly young Apache project.
Its release process is work in progress
+ and is modeled from [[http://wiki.apache.org/hadoop/HowToRelease|Hadoop Release Procedure]].
  
  Note that only Pig commiters can create a release.
  
@@ -13, +14 @@

  
  We only branch for major (X.0.0) and minor(X.Y.0) releases but not for patches (X.Y.Z).
Patch is and update to an existing branch created for X.Y.0.
  
-  1. Send email to `pig-dev@hadoop.apache.com` to notify that you about to branch the tree
and ask to hold off any commits till this is finished.
+  1. Send email to `dev@pig.apache.com` to notify that you about to branch the tree and ask
to hold off any commits till this is finished.
   2. Update `CHANGES.txt` to include the release version and date (use `Unreleased` for the
date if it is unknown) and remove `Trunk (unreleased changes)`. Below is the example of the
top of the `CHANGES.txt` file after the update:{{{
  Pig Change Log
  
@@ -34, +35 @@

  svn commit -m "Preparing for release X.Y.Z"
  }}}
   4. Create a branch for the release series:{{{
- svn copy https://svn.apache.org/repos/asf/hadoop/pig/trunk \
+ svn copy https://svn.apache.org/repos/asf/pig/trunk \
- https://svn.apache.org/repos/asf/hadoop/pig/branches/branch-X.Y -m "Branching for X.Y releases"
+ https://svn.apache.org/repos/asf/pig/branches/branch-X.Y -m "Branching for X.Y releases"
  }}}
   5. Update CHANGES.txt to add back in Trunk (unreleased changes). Top of the `CHANGES.txt`
should look like this now:{{{
  Pig Change Log
@@ -63, +64 @@

  The steps in this section are needed for all the releases (major, minor, and patches).
  
   1. Check out the branch with:{{{
- svn co https://svn.apache.org/repos/asf/hadoop/pig/branches/branch-X.Y
+ svn co https://svn.apache.org/repos/asf/pig/branches/branch-X.Y
  }}}
   2. Run rat report and make sure that all files that can have apache license agreement.
Note that currently the rat report is part of output and needs to be manually extracted. TODO:
write the report into a file.{{{
  ant -Djava5.home=<java5 jdk dir>  -Dforrest.home=<forrest installation dir>
releaseaudit >out
@@ -78, +79 @@

  svn commit -m "Preparing for release X.Y.Z"
  }}}
   6. Tag the release candidate:{{{
- svn copy https://svn.apache.org/repos/asf/hadoop/pig/branches/branch-X.Y \
+ svn copy https://svn.apache.org/repos/asf/pig/branches/branch-X.Y \
- https://svn.apache.org/repos/asf/hadoop/pig/tags/release-X.Y.Z-rcR -m "Pig X.Y.Z-rcR release."
+ https://svn.apache.org/repos/asf/pig/tags/release-X.Y.Z-rcR -m "Pig X.Y.Z-rcR release."
  }}}
  
  == Building ==
@@ -123, +124 @@

  gpg --armor --output pubkey.txt --export 'Your Name'
  }}}
     a. Open pubkey.txt, copy the full text and append it to the following files by pasting,
then commit these changes: {{{
- https://svn.apache.org/repos/asf/hadoop/pig/branches/branch-X.Y.Z/KEYS
+ https://svn.apache.org/repos/asf/pig/branches/branch-X.Y.Z/KEYS
- https://svn.apache.org/repos/asf/hadoop/pig/trunk/KEYS
+ https://svn.apache.org/repos/asf/pig/trunk/KEYS
  }}}
     a. Upload updated KEYS to Apache. {{{
- scp KEYS people.apache.org:/www/www.apache.org/dist/hadoop/pig/KEYS
+ scp KEYS people.apache.org:/www/www.apache.org/dist/pig/KEYS
  }}}
     a. Export your private key, keep it with you. {{{
  gpg --export-secret-key -a "Your Name" > private.key
@@ -145, +146 @@

  cd ..
  scp RELEASE_NOTES.txt people.apache.org:public_html/pig-X.Y.Z-candidate-0
  }}}
-  8. Call a release vote. The initial email should be sent to `pig-dev@hadoop.apache.org`.
Make sure to attache rat report to it. Here is a sample of email: {{{
+  8. Call a release vote. The initial email should be sent to `dev@pig.apache.org`. Make
sure to attache rat report to it. Here is a sample of email: {{{
  From: Olga Natkovich [mailto:olgan@yahoo-inc.com] 
  Sent: Tuesday, November 25, 2008 3:59 PM
- To: pig-dev@hadoop.apache.org
+ To: dev@pig.apache.org
  Subject: [VOTE] Release Pig 0.1.1 (candidate 0)
  
  Hi,
@@ -161, +162 @@

  
  The rat report is attached.
  
- Keys used to sign the release are available at http://svn.apache.org/viewvc/hadoop/pig/trunk/KEYS?view=markup.
+ Keys used to sign the release are available at http://svn.apache.org/viewvc/pig/trunk/KEYS?view=markup.
  
  Please download, test, and try it out:
  
@@ -172, +173 @@

  Olga
  }}}
  
- Forward the initial email to `private@hadoop.apache.org` for Hadoop PMC members to vote.
+ Forward the initial email to `private@pig.apache.org` for Pig PMC members to vote.
  
  == Publish ==
  
  Once [[http://www.apache.org/foundation/voting.html#ReleaseVotes|three PMC members have
voted for a release]], it may be published.
  
   1. Tag the release: {{{
- svn move https://svn.apache.org/repos/asf/hadoop/pig/tags/release-X.Y.Z-rcR \
+ svn move https://svn.apache.org/repos/asf/pig/tags/release-X.Y.Z-rcR \
- https://svn.apache.org/repos/asf/hadoop/pig/tags/release-X.Y.Z -m "Pig X.Y.Z release."
+ https://svn.apache.org/repos/asf/pig/tags/release-X.Y.Z -m "Pig X.Y.Z release."
  }}}
-  2. Copy release files to the distribution directory and make them writable by the hadoop
group.{{{
+  2. Copy release files to the distribution directory and make them writable by the pig group.{{{
  ssh people.apache.org
- cp -pr public_html/pig-X.Y.Z-candidate-0 /www/www.apache.org/dist/hadoop/pig/pig-X.Y.Z
+ cp -pr public_html/pig-X.Y.Z-candidate-0 /www/www.apache.org/dist/pig/pig-X.Y.Z
- cd /www/www.apache.org/dist/hadoop/pig
+ cd /www/www.apache.org/dist/pig
- chgrp -R hadoop pig-X.Y.Z
+ chgrp -R pig pig-X.Y.Z
  chmod -R g+w pig-X.Y.Z
  }}}
   3. 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/pig
+ cd /www/www.apache.org/dist/pig
  rm -rf pig-A.B.C; rm stable
  ln -s pig-A.B.D stable
  }}}
   4. Wait 24 hours for release to propagate to mirrors.
   5. Prepare to edit the website.{{{
- svn co https://svn.apache.org/repos/asf/hadoop/pig/site
+ svn co https://svn.apache.org/repos/asf/pig/site
  }}}
   6. Update the front page news in author/src/documentation/content/xdocs/index.xml.
   7. Update the release news in author/src/documentation/content/xdocs/releases.xml.
@@ -211, +212 @@

   10. Regenerate the site, review it and commit in HowToCommit.
   11. Deploy your site changes.{{{
  ssh people.apache.org
- cd /www/hadoop.apache.org/pig
+ cd /www/pig.apache.org
  svn up
  }}}
   12. Wait until you see your changes reflected on the Apache web site.
   13. Send announcements to the user and developer lists as well as (`announce@haoop.apache.org`)
once the site changes are visible. {{{
  Pig  team is happy to announce Pig X.Y.Z release. 
  
- Pig is Hadoop subproject which provides high-level data-flow language and execution framework
for parallel computation on Hadoop clusters.
+ Apache Pig provides a high-level data-flow language and execution framework for parallel
computation on Hadoop clusters.
- More details about Pig can be found at http://hadoop.apache.org/pig/.
+ More details about Pig can be found at http://pig.apache.org/.
  
- The highlights of this release are ... The details of the release can be found at http://hadoop.apache.org/pig/releases.html.
+ The highlights of this release are ... The details of the release can be found at http://pig.apache.org/releases.html.
  }}}
   14. In JIRA, mark the release as released.
     a. Goto JIRA and click on Administration tab.
@@ -246, +247 @@

     a. Click "Confirm".  Don't worry if it gives you a HTTP 500 error, it still does the
transitions.
  
   16. Update jdiff for next release (step 16 to 19). {{{
-    svn co https://svn.apache.org/repos/asf/hadoop/pig/trunk
+    svn co https://svn.apache.org/repos/asf/pig/trunk
  }}}
   17. Open build.xml. Change this line: {{{
  <property name="jdiff.stable" value="X.Y-1.Z"/>

Mime
View raw message