Page History

...

1. Tag the release:

   Code Block
   svn move https://svn.apache.org/repos/asf/incubator/hcatalog/tags/release-X.Y.Z-rcR \ https://svn.apache.org/repos/asf/incubator/hcatalog/tags/release-X.Y.Z -m "HCatalog X.Y.Z release."

2. Copy release files to the distribution directory and make them writable by the hcatalog group.

   Code Block
   ssh people.apache.org cp -pr public_html/hcatalog-X.Y.Z-incubating-candidate-0 /www/www.apache.org/dist/incubator/hcatalog/hcatalog-X.Y.Z-incubating cd /www/www.apache.org/dist/incubator/hcatalog chgrp -R incubator hcatalog-X.Y.Z-incubating chmod -R g+w hcatalog-X.Y.Z-incubating

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.

   Code Block
   ssh people.apache.org cd /www/www.apache.org/dist/incubator/hcatalog rm -rf hcatalog-A.B.C-incubating; rm stable ln -s hcatalog-X.Y.Z-incubating stable

4. Wait 24 hours for release to propagate to mirrors.
5. Prepare to edit the website.

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

6. Update the front page news: author/src/documentation/content/xdocs/index.xml
7. Update the release news: author/src/documentation/content/xdocs/releases.xml
8. Update the documentation links: author/src/documentation/content/xdocs/site.xml
9. Copy in the release specific documentation. releasedir in the following is the directory where you built the release version of HCatalog

   Code Block
   cd publish mkdir docs/rX.Y.Z cp -pr <releasedir>/build/hcatalog-X.Y.Z-incubating/docs/* publish/docs/rX.Y.Z/ svn add publish/docs/rX.Y.Z

10. We should only be publishing release specific documentation for releases still available for download. If you removed any releases from /www/www.apache.org/dist/incubator/hcatalog several steps ago, then you should also use svn rm to remove the associated documents from docs.
11. Regenerate the site, review it and commit in HowToCommit.
12. Deploy your site changes.

    Code Block
    ssh people.apache.org cd /www/incubator.apache.org/content/hcatalog svn up

13. Wait until you see your changes reflected on the Apache web site.
14. Send announcements to the user and developer lists as well as (general@haoop.apache.org) once the site changes are visible.

    Code Block
    The HCatalog team is happy to announce the release of HCatalog X.Y.Z. Apache HCatalog provides a table management service for Hadoop. More details about HCatalog can be found at http://incubator.apache.org/hcatalog. The highlights of this release are ... The details of the release can be found at http://incubator.apache.org/hcatalog/releases.html.

15. In JIRA, mark the release as released.
    1. Goto JIRA and click on Administration tab.
    2. Select the HCatalog project.
    3. Select Manage 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 Edit Details 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 Version box at the top of the page.
16. 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 HCatalog.
    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 HCatalog 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.
17. Update jdiff for next release (We don't have jdiff set up yet, but these next several instructions are left here so when we do we can use them)

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

    1. 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"/>

    2. Copy jdiff comparison base to trunk

       Code Block
       cp {releasedir}/lib/jdiff/hcatalog_X.Y.Z.xml lib/jdiff svn add lib/jdiff/hcatalog_X.Y.Z.xml svn remove lib/jdiff/hcatalog_X.Y-1.Z.xml svn commit -m "Jdiff change for X.Y.Z"