Versions Compared

Old Version 48

changes.mady.by.user Lefty Leverenz

Saved on

compared with

New Version 49

changes.mady.by.user Alan Gates

Saved on

Key

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

This page is prepared for Hive committers. You need committer rights to create a new Hive release.

Table of Contents

Info
titleMaven Version Warning

This page assumes you are releasing from the master branch, and thus omits the use of maven profiles to determine which version of Hadoop you are building against. If you are releasing from branch-1, you will need to add -Phadoop-2 to most of your maven commands.

Preparation

  1. Bulk update Jira to unassign from this release all issues that are open non-blockers and send follow-up notification to the developer list that this was done.
  2. Run 'mvn clean apache-rat:check -Phadoop-2' and examine the generated report for any files, especially .java files which should all have Apache license headers. Note also, that each individual component will have a rat.txt inside it when you run this – be sure to check ql/target/rat.txt, for example. Add the license header to any file that is missing it (open a jira and submit a patch).
  3. Update copyright date in NOTICE. If any components mentioned in them have updated versions, you would need to update the copyright dates for those. (Thejas comment: It sounds like entries are needed in NOTICE only if the license requires such attribution. See http://www.apache.org/legal/src-headers.html#notice.)

...

  1. Make sure your release notes have been updated for any new commits, and go through the previous steps if necessary.

  2. Build the release (binary and source versions) after running unit tests. Manually create the md5 files. On a Mac use md5 in place of md5sum.

    No Format
    % mvn install -Pdist -DskipTests -Phadoop-2 -Dmaven.javadoc.skip=true -DcreateChecksum=true

% cd packaging/target
% md5 apache-hive-0.13.0-bin.tar.gz > apache-hive-X.Y.Z-bin.tar.gz.md5
% md5 apache-hive-0.13.0-src.tar.gz > apache-hive-X.Y.Z-src.tar.gz.md5

  3. Verify that the MD5 checksums are valid:

    No Format
    % md5sum -c hive-X.Y.Z.tar.gz.md5
hive-X.Y.Z.tar.gz: OK

% md5sum -c hive-X.Y.Z-bin.tar.gz.md5
hive-X.Y.Z-bin.tar.gz: OK
  4. Check that release file looks ok -- e.g., install it and run examples from tutorial.
  5. Setup your PGP keys for signing the release, if you don't have them already.
    1. See http://www.apache.org/dev/release-signing.html, http://www.apache.org/dev/openpgp.html.

  6. Sign the release (see Step-By-Step Guide to Mirroring Releases for more information).

    No Format
    % gpg --armor --output apache-hive-X.Y.Z-bin.tar.gz.asc --detach-sig apache-hive-X.Y.Z-bin.tar.gz
% gpg --armor --output apache-hive-X.Y.Z-src.tar.gz.asc --detach-sig apache-hive-X.Y.Z-src.tar.gz

  7. Copy release files to a public place.

    No Format
    % ssh people.apache.org mkdir public_html/hive-X.Y.Z-candidate-0
% scp -p apache-hive-X.Y.Z*.tar.gz* people.apache.org:public_html/apache-hive-X.Y.Z-candidate-0

  8. Publish Maven artifacts to the Apache staging repository:

    No Format
    % mvn deploy -DskipTests -Phadoop-2 -Papache-release -Dmaven.javadoc.skip=true
  9. Login to the Apache Nexus server and "close" the staged repository. This makes the artifacts available at a temporary URL.

...

  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. Note that you need PMC privileges to do this step – if you do not have such privileges, please ping a PMC member to do this for you.

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

  4. 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

  5. Check out the javadocs svn repository as follows:

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

  6. 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

    If this is a bugfix release, svn rm the obsoleted version. (For eg., when committing javadocs for r0.13.1, r0.13.0 would have been removed)

  7. Prepare to edit the website.

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

  8. 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
    languagetext
    ./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.

  9. 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.

  10. 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.

  11. Login to the Apache Nexus server and mark the release candidate artifacts as released.

  12. 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

...