Dear Wiki user,

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

The following page has been changed by OlgaN:
http://wiki.apache.org/pig/HowToRelease

------------------------------------------------------------------------------
  
  Note that only Pig commiters can create a release.
  
+ == Preparation ==
+ 
+ TODO:
+  1. define issue management process like assigning/removing issues from 
release]
+ 
+ == Creating Release Branch ==
+ 
+ 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 [EMAIL PROTECTED] 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
+ 
+ Release 0.1.1 - Unreleased
+ 
+ INCOMPATIBLE CHANGES
+ 
+ NEW FEATURES
+ 
+ IMPROVEMENTS
+ PIG-253: integration with hadoop-18
+ 
+ BUG FIXES
+ PIG-342: Fix DistinctDataBag to recalculate size after it has spilled. 
(bdimcheff via gates)
+ }}}
+  3. Commit these changes to trunk:
+ {{{
+ 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 \
+ https://svn.apache.org/repos/asf/hadoop/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
+ 
+ Trunk (unreleased changes)
+ 
+   INCOMPATIBLE CHANGES
+ 
+   IMPROVEMENTS
+ 
+   OPTIMIZATIONS
+ 
+   BUG FIXES
+ 
+ Release 0.1.1 - Unreleased
+ ....
+ }}}
+  6. Update the default version in `build.xml` on trunk to X.Y+1.0-dev.
+  7. Commit these changes to trunk:
+ {{{
+ svn commit -m "Preparing for X.Y+1.0 development"
+ }}}
+ 
+ TODO:
+  1. Add documentation update the process once we integrate the documentation 
into forrect. (Will need docs target in build.xml)
+ 

Reply via email to