Page History

...

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

2. Create and publish the tag:

   Code Block
   language text
   git tag storage-release-X.Y.Z-rcR -m "Hive Storage API X.Y.Z-rcR release." git push origin storage-release-X.Y.Z-rcR

   
   

3. Build the release (binary and source versions) after running unit tests. Manually create the sha file.

   No Format
   % wget https://github.com/apache/hive/archive/storage-release-X.Y.Z-rcR.tar.gz % tar xzvf storage-release-X.Y.Z-rcR.tar.gz % mv storage-release-X.Y.Z-rcR/storage-api hive-storage-X.Y.Z % tar czvf hive-storage-X.Y.Z-rcR.tar.gz hive-storage-X.Y.Z % shasum -a 256 hive-storage-X.Y.Z-rcR.tar.gz > hive-storage-X.Y.Z-rcR.tar.gz.sha256

   
   

4. Setup your PGP keys for signing the release, if you don't have them already.
   
   1. See httphttps://www.apache.org/dev/release-signing.html, httphttps://www.apache.org/dev/openpgp.html.

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

   No Format
   % gpg --armor --detach-sig hive-storage-X.Y.Z-rcR.tar.gz

   
   

6. Check the signatures.

   No Format
   % shasum -c hive-storage-X.Y.Z-rcR.tar.gz.sha256 hive-storage-X.Y.Z-rcR.tar.gz: OK   % gpg hive-storage-X.Y.Z-rcR.tar.gz.asc gpg: assuming signed data in `hive-storage-X.Y.Z-rcR.tar.gz' gpg: Signature made Fri Apr 28 12:50:03 2017 PDT using RSA key ID YOUR-KEY-ID gpg: Good signature from "Your Name <YOUR-APACHE-ID@apache.org>"

   
   

7. Copy release files to a public place.

   No Format
   % sftp YOUR-APACHE-ID@home.apache.org sftp> cd public_html sftp> mkdir hive-storage-X.Y.Z sftp> cd hive-storage-X.Y.Z sftp> put hive-storage-X.Y.Z-rcR.tar.gz* sftp> quit

   
   

8. Send email to dev@hive.apache.org calling the vote.

...

% svn checkout https://dist.apache.org/repos/dist/release/hive hive-dist
% cd hive-dist
% mkdir hive-storage-X.Y.Z
% cd hive-storage-X.Y.Z
% wget httphttps://home.apache.org/~YOUR-APACHE-ID/hive-storage-X.Y.Z/hive-storage-X.Y.Z-rcR.tar.gz{,.sha256,.asc}
% svn add .
% svn commit

...

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. There are two kinds of JIRAs that need to be taken care of:
   1. Unresolved JIRAs with Target Version/s or Fix Version/s (legacy) set to the release in question.
   2. Resolved/closed(!) JIRAs with Target Version/s, but not Fix Version/s set to the release in question (e.g. a JIRA targets 2.0.0 and 1.3.0, but was only committed to 2.0.0).
2. Run 'mvn clean apache-rat:check' 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 httphttps://www.apache.org/legal/src-headers.html#notice.)

Branching

Skip this section if this is NOT the first release in a series (i.e., release X.Y.0).

...

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 sha256 files.

   No Format
   % mvn install -Pdist -DskipTests -Dmaven.javadoc.skip=true -DcreateChecksum=true % cd packaging/target % shasum -a 256 apache-hive-X.Y.Z-bin.tar.gz > apache-hive-X.Y.Z-bin.tar.gz.sha256 % shasum -a 256 apache-hive-X.Y.Z-src.tar.gz > apache-hive-X.Y.Z-src.tar.gz.sha256

   
   

3. Verify that the SHA 256 checksums are valid:

   No Format
   % shasum -a 256 -c apache-hive-X.Y.Z-bin.tar.gz.sha256 apache-hive-X.Y.Z-bin.tar.gz: OK % shasum -a 256 -c apache-hive-X.Y.Z-src.tar.gz.sha256 apache-hive-X.Y.Z-src.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 https://www.apache.org/dev/release-signing.html, http https://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
   % sftp YOUR-APACHE-ID@home.apache.org sftp> cd public_html sftp> mkdir apache-hive-X.Y.Z-rc-0 sftp> cd apache-hive-X.Y.Z-rc-0 sftp> put apache-hive-X.Y.Z*.tar.gz* sftp> quit

   
   

8. Publish Maven artifacts to the Apache staging repository. Make sure to have this setup for Apache releases.  (If you get an error gpg: signing failed: Inappropriate ioctl for device trying doing export GPG_TTY=$(tty) .)

   No Format
   % mvn deploy -DskipTests -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. Call a release vote on dev at hive.apache.org.

   No Format

   From: you@apache.org To: dev@hive.apache.org Subject: [VOTE] Apache Hive X.Y.Z Release Candidate N Apache Hive X.Y.Z Release Candidate N is available here: httphttps://people.apache.org/~you/hive-X.Y.Z-candidate-N Maven artifacts are available here: https://repository.apache.org/content/repositories/orgapachehive-121/ SourceThe tag for RCN is at: http://svn.apache.org/viewvc/hive/tagsrelease-X.Y.Z-rcR has been applied to the source for this release in github, you can see it at https://github.com/apache/hive/tree/release-X.Y.Z-RCN/rcR Voting will conclude in 72 hours. Hive PMC Members: Please test and vote. Thanks.

   
   

...

1. Verifying the PGP signature:

   No Format
   #get the hive committers keys file wget httphttps://www.apache.org/dist/hive/KEYS or wget https://people.apache.org/keys/group/hive.asc gpg --import <keys file> gpg --verify hive-X.Y.Z-bin.tar.gz.asc hive-X.Y.Z-bin.tar.gz gpg --verify hive-X.Y.Z.tar.gz.asc hive-X.Y.Z.tar.gz

   
   

2. Verifying the sha256 checksum:
   See the step under Building.

...

1. Tag the release and delete the release candidate tag:

   No Format
   git tag -s rel/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 rel/release-X.Y.Z git tag -d release-X.Y.Z-rcR git push origin :release-X.Y.Z-rcR

   
   

2. Follow instructions in httphttps://www.apache.org/dev/release-publishing.html#distribution to push the new release artifacts to httphttps://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 -DskipTests -Dadditionalparam=-Xdoclint:none

   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
   language text
   ./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 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, among others: * 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, Apache Tez and Apache Spark 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

    
    

...