Page History

...

1. Tag the release:

   Code Block
   svn move https://svn.apache.org/repos/asf/pig/tags/release-X.Y.Z-rcR \ 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 pig group.

   Code Block
   ssh people.apache.org 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/pig chgrp -R pig pig-X.Y.Z chmod -R g+w pig-X.Y.Z

3. The release directory usually contains just three releases, the most recent from three branches, with a link named 'stablelatest' to the most recent recommended version.

   Code Block
   ssh people.apache.org cd /www/www.apache.org/dist/pig rm -rf pig-A.B.C; rm stablelatest ln -s pig-A.B.D stablelatest

4. Push Maven release from staging to production
   1. Go to https://repository.apache.org/index.html#view-repositories;staging~browsestorage
   2. Log in, using your Apache LDAP credentials. The sign in link is in the upper right hand corner.
   3. In the frame on the left side of the page, select "Staging Repositories", you should now see a list of artifacts in the main frame.
   4. Select the appropriate artifacts for this release and click "Close" on the bar above the list of artifacts.
   5. Select the appropriate artifacts for this release and click "Release" on the bar above the list of artifacts.
5. Wait 24 hours for release to propagate to mirrors.

6. Prepare to edit the website.

   Code Block
   svn co https://svn.apache.org/repos/asf/pig/site

7. Update the front page news in author/src/documentation/content/xdocs/index.xml.
8. Update the release news in author/src/documentation/content/xdocs/releases.xml.
9. Update the documentation links in author/src/documentation/content/xdocs/site.xml

10. Copy in the release specific documentation

    Code Block
    mkdir publish/docs/rX.Y.Z cp -pr <releasedir>/docs/* publish/docs/rX.Y.Z/ svn add publish/docs/rX.Y.Z

11. Regenerate the site, review it and commit in HowToDocument#UpdatingthePigSiteDocumentation.
12. Wait until you see your changes reflected on the Apache web site. This might take a few minutes.

13. Send announcements to the user and developer lists as well as (dev@pig.apache.org; user@pig.apache.org; announce@apache.org; general@hadoop.apache.org) once the site changes are visible. Note that emails sent to announce@apache.org must be sent from your apache.org email address and you must be subscribed to each of the lists.

    Code Block
    [ANNOUNCE] Apache Pig X.Y.Z released The Pig team is happy to announce the Pig X.Y.Z release. 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://pig.apache.org/. 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.
    1. Goto JIRA and click on Administration tab.
    2. Select the Pig project.
    3. Select Versions.
    4. Select Release for the version you have released.
    5. If a description has not yet been added for the version you are releasing, select Add description and give a brief description of the release.
    6. If the next version does not exist (that is, if you are releasing version 0.x, if version 0.x+1 does not yet exist) create it using the Add box at the top of the page.
15. In JIRA, mark the issues resolved in this release as closed.
    1. Goto JIRA and click on the "Search for Issues" on "Issues" menu.
    2. In the left hand Edit section, set Project to Pig.
    3. In Status select "Resolved"
    4. In Resolutions select "Fixed"
    5. Click "Search" button
    6. In the next screen, further select fix For select the version you are releasing.
    7. Click on the "Search" button
    8. Select "Tools->Bulk change all XX issues" (near the top right)
    9. Select all the issues and click on "Next"
    10. Select "Transition Issues" radio button and click on "Next"
    11. Select "Close Issue" radio button and click on "Next"
    12. Uncheck the box near the bottom at says "Send mail for this update" lest you spam every Pig developer with a message for every bug resolved in this release. Click "Next".
    13. 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).

    Code Block
    svn co https://svn.apache.org/repos/asf/pig/trunk

17. Open build.xml. Change this line:

    Code Block
    <property name="jdiff.stable" value="X.Y-1.Z"/> To <property name="jdiff.stable" value="X.Y.Z"/>

18. Copy jdiff comparison base to trunk

    Code Block
    cp {releasedir}/lib/jdiff/pig_X.Y.Z.xml lib/jdiff

19. Code Block
    svn add lib/jdiff/pig_X.Y.Z.xml svn remove lib/jdiff/pig_X.Y-1.Z.xml svn commit -m "Jdiff change for X.Y.Z"

    TODO Need to integrate javadoc into this.

...