Versions Compared

Old Version 27

changes.mady.by.user Thejas Nair

Saved on

compared with

New Version 28

changes.mady.by.user Aniket Mokashi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Send email to dev@pig.apache.org 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:

    Code Block
    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. Edit src/docs/src/documentation/content/xdocs/site.xml. In the external reference for api where the link contains the previous version number change this string to the correct version number.

  4. Commit these changes to trunk:

    Code Block
    svn commit -m "Preparing for release X.Y.Z"

  5. Create a branch for the release series:

    Code Block
    svn copy https://svn.apache.org/repos/asf/pig/trunk \
https://svn.apache.org/repos/asf/pig/branches/branch-X.Y -m "Branching for X.Y releases"

  6. Update CHANGES.txt to add back in Trunk (unreleased changes). Top of the CHANGES.txt should look like this now:

    Code Block
    Pig Change Log

Trunk (unreleased changes)

  INCOMPATIBLE CHANGES

  IMPROVEMENTS

  OPTIMIZATIONS

  BUG FIXES

Release 0.1.1 - Unreleased
....
  7. Update the default version in build.xml on trunk to X.Y+1.0-dev.

  8. Commit these changes to trunk:

    Code Block
    svn commit -m "Preparing for X.Y+1.0 development"

...