Page History

...

1. Tag the release:

   No Format
   git tag -a release-X.Y.Z release-X.Y.Z-rcR -m "HiveX.Y.Z release." # where -rcR was the last tagged release candidate that passed the vote git push origin release-X.Y.Z

2. Follow instructions in http://www.apache.org/dev/release-publishing.html#distribution to push the new release artifacts to  http://www.apache.org/dist/ , making sure to create a new directory for the new release, and re-linking the stable link to the latest build.

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.

4. TODO : document is currently in the process of being edited - saving half way

   No Format
   ssh people.apache.org cd /www/www.apache.org/dist/hive rm -rf hive-A.B.C; rm stable ln -s hive-A.B.D stable

5. Wait 24 hours for release to propagate to mirrors.

6. Prepare to edit the website.

   No Format
   svn co https://svn.apache.org/repos/asf/hive/site

7. Wait 24 hours for release to propagate to mirrors.

8. In your base hive source directory, generate javadocs as follows:

   No Format
   mvn clean install javadoc:javadoc javadoc:aggregate -Phadoop-2 -DskipTests

   After you run this, you should have javadocs present in your <hive_source_dir>/target/site/apidocs

9. Check out the javadocs svn repository as follows:

   No Format
   svn co https://svn.apache.org/repos/infra/websites/production/hive/content/javadocs

10. Copy the generated javadocs from the source repository to the javadocs repository, add and commit:

    No Format
    mkdir <hive_javadocs_repo_dir>/rX.Y.Z/ cd <hive_javadocs_repo_dir> cp -r <hive_source_dir>/target/site/apidocs ./rX.Y.Z/api svn add rX.Y.Z svn commit

    Copy the new release docs to publish/docs/rX.Y.Z:

    Code Block
    tar xvf hive-X.Y.Z.tar.gz '*/docs' mv hive-X.Y.Z/docs publish/docs/rX.Y.Z svn add publish/docs/rX.Y.Z

    If this is a bugfix release, delete svn rm the documentation for the obsoleted release.

    Code Block
    svn rm publish/docs/rX.Y.Z-1

11. Update the documentation links in author/src/documentation/content/xdocs/site.xml.
12. Update the release news in author/src/documentation/content/xdocs/releases.xml.
13. Update publish/.htaccess with the current release and any new redirects for obsoleted releases.

14. version. (For eg., when committing javadocs for r0.13.1, r0.13.0 would have been removed)

15. Prepare to edit the website.

    No Format
    svn co https://svn.apache.org/repos/asf/hive/cms/trunk

16. Edit files content/downloads.mdtext and javadoc.mdtext to appropriately add entries for the new release in the appropriate location. For example, for 1.2.0, the entries made were as follows:

    Code Block

    ./content/downloads.mdtext:### 18 May 2015 : release 1.2.0 available ./content/downloads.mdtext:You can look at the complete [JIRA change log for this release][HIVE_1_2_0_CL]. ./content/downloads.mdtext:[HIVE_1_2_0_CL]: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329345&styleName=Text&projectId=12310843 ./content/javadoc.mdtext: * [Hive 1.2.0 Javadocs][r1.2.0] ./content/javadoc.mdtext:[r1.2.0]: /javadocs/r1.2.0/api/index.html

    As you can see, you will need a release note link for this release as created previously for this section.

17. Go to https://hive.staging.apache.org/hive/ , get the hive working copy, force a new copy if you don't see your changes yet, and then ask it to publish the new copy. That should update the downloads and javadocs page as per the changes you made to downloads.mdtext, javadoc.mdtext earlier, and also make available the new javadocs. If you don't see it yet, you may have to wait 24 hours - it should be there by then.

    Regenerate the site, review it, then commit it. The live site is automatically deployed from subversion after a few minutes.

    Code Blockant -Dforrest.home=/usr/local/forrest -Djava5.home=/usr/local/jdk1.5 firefox publish/index.html svn commit -m "Updated site for release X.Y.Z."

18. Update JIRA
    1. Ensure that only issues in the "Fixed" state have a "Fix Version" set to release X.Y.Z.
    2. Release the version. Visit the "Administer Project" page, then the "Manage versions" page. You need to have the "Admin" role in Hive's Jira for this step and the next.
    3. Close issues resolved in the release. Disable mail notifications for this bulk change.
       
       
19. Login to the Apache Nexus server and mark the release candidate artifacts as released.
    
    

20. Send a release announcement to Hive user and dev lists as well as the Apache announce list. This email should be sent from your Apache email address:

    No Format

    From: you@apache.org To: user@hive.apache.org, dev@hive.apache.org, announce@apache.org Subject: [ANNOUNCE] Apache Hive X.Y.Z Released The Apache Hive team is proud to announce the the release of Apache Hive version X.Y.Z. The Apache Hive (TM) data warehouse software facilitates querying and managing large datasets residing in distributed storage. Built on top of Apache Hadoop (TM), it provides: * Tools to enable easy data extract/transform/load (ETL) * A mechanism to impose structure on a variety of data formats * Access to files stored either directly in Apache HDFS (TM) or in other data storage systems such as Apache HBase (TM) * Query execution via Apache Hadoop MapReduce and Apache Tez frameworks. For Hive release details and downloads, please visit: https://hive.apache.org/downloads.html Hive X.Y.Z Release Notes are available here: [UPDATE THIS LINK] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310843&version=12316178 We would like to thank the many contributors who made this release possible. Regards, The Apache Hive Team

...