Page History

...

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

Preparation

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.
run 'ant rat' to and examine the generated report for any files, specially .java files should be having apache license headers. Add the license header to any file that is missing it (open a jira and submit a patch).
Update copyright date in NOTICE . If the components mentioned in them have updated version, 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)

Branching

Storage API Release

The Hive projects has two products that are released separately:

Storage-API – the vectorization and predicate push down classes
Hive – the rest of Hive

Most Hive releases will require a new storage-api release and the storage-api currently releases faster than Hive, so has higher version numbers.

Storage API Prepare Master Branch

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

Notify developers on the #hive IRC channel that you are about to branch a release.

Check out the master branch
Code Block
language text
git checkout master
Increment the value of the version property in the storage-api/pom.xml file. For example, if the current value is 2.5.0-SNAPSHOT, the new value should be 2.6.0-SNAPSHOT. Please note that the SNAPSHOT suffix

Create a branch for the release series:

Code Block
svn copy https://svn.apache.org/repos/asf/hive/trunk \ https://svn.apache.org/repos/asf/hive/branches/branch-X.Y -m "Branching for X.Y releases"

Increment the value of the version property the build.properties file, hcatalog/build.properties and hcat pom.xml files (find hcatalog/ -name pom.xml), on trunk For example, if the current value is 0.7.0-SNAPSHOT, the new value should be 0.8.0-SNAPSHOT. Please note that the SNAPSHOT suffix
is required in order to indicate that this is an unreleased development branch.
Verify that the build is working with changes
Update the storage-api.version property in the root pom.xml and standalone-metastore/pom.xml to the new value from the step above.
Verify that the build is working with changes.
Commit these changes to master with a comment "Preparing for storage-api
Commit these changes to trunk. Code Block svn commit -m "Preparing for
X.Y+1.0

development"

Updating Release Branch

These operations take place in the release branch.

.

Storage API Branching

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

Notify developers on the #hive IRC channel and dev@hive mailing lists that you are about to branch a release.
Create a branch for the release series:
Code Block
language text
git checkout -b storage-branch-X.Y origin/master

Check out the release branch with:

Code Block
svn co https://svn.apache.org/repos/asf/hive/branches/branch-X.Y

Update the version property value in the build.properties file, hcatalog/build.properties and hcat pom.xml files (find hcatalog/ -name pom.xml). You should remove the SNAPSHOT suffix and set version equal to hive-X.Y.Z where
Update the version property value in the storage-api/pom.xml file. You should remove the SNAPSHOT suffix and set version equal to X.Y.Z where
Z is the point release number in this release series (0 for the first one, in which case this step is a no-op since you already did this above when creating the branch). Use Maven's Versions plugin to do this as follows:
Verify that the build is working with changes.
Commit these changes with a comment "Preparing for storage-api X.Y.Z release".

Tag the release candidate (R is the release candidate number, and also starts from 0):

Code Block

language	text

git
svn commit -a -m "Preparing for releasestorage-api X.Y.Z"

If not already done, merge desired patches from trunk into the branch and commit these changes. We don't currently use svn merge for this, but if we did, the script would be

Code Block


cd  release"
git push -u origin storage-branch-X.Y
svngit mergetag -rR1:R2 ../trunk .
svn commit a storage-release-X.Y.Z-rcR -m "MergeHive -r R1:R2 from trunk to Storage API X.Y.Z-rcR branchrelease. Fixes: HIVE-A, HIVE-B."
"
git push origin storage-release-X.Y.Z-rcR

Making Storage API Release Artifacts

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

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

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-

You probably also want to commit a patch (on both trunk and branch) which updates README.txt to bring it up to date (at a minimum, search+replacing references to the version number). Also check NOTICE to see if anything needs to be updated for recent library dependency changes or additions.
1. Select all of the JIRA's for the current release that aren't FIXED and do bulk update to clear the 'Fixed Version' field.
2. Likewise, use JIRA's Release Notes link to generate content for the RELEASE_NOTES.txt file. Be sure to select 'Text' format. (It's OK to do this with a direct commit rather than a patch.)

Tag the release candidate (R is the release candidate number, and also starts from 0):

Code Block


svn copy https://svn.apache.org/repos/asf/hive/branches/branch-X.Y \
https://svn.apache.org/repos/asf/hive/tags/release-X.Y.Z-rcR/storage-api -m "Hive hive-storage-X.Y.Z
% tar czvf hive-storage-X.Y.Z-rcR release."

Building

Make sure your the release notes have been updated for any new commits, and go through the previous steps if necessary.
Build the release (binary and source versions) after running unit tests. Note that this will generate MD5 checksum files automatically.
No Format
% ant -Dversion=X.Y.Z clean test tar binary

Verify that the MD5 checksums are valid:

No Format
% md5sum -c hive.tar.gz hive-storage-X.Y.Z % shasum -a 256 hive-storage-X.Y.Z.tar.gz.md5 hive-X.Y.Z.-rcR.tar.gz: OK % md5sum -c hive> hive-storage-X.Y.Z-binrcR.tar.gz.md5 hive-X.Y.Z-bin.tar.gz: OK

Check that release file looks ok - e.g. install it and run examples from tutorial.
sha256
Setup your PGP Setup your PGP keys for signing the release, if you don't have it them already.
1. See https
2. See http://www.apache.org/dev/release-signing.html, https://www.apache.org/dev/openpgp.html.
Sign the release (
see
see Step-By-Step Guide to Mirroring Releases
for
for more information).
No Format
% gpg --armor --outputdetach-sig hive-storage-X.Y.Z-rcR.tar.gz.asc --detach-sig

Check the signatures.

No Format
% shasum -c hive-storage-X.Y.Z-rcR.tar.gz % gpg --armor --output hive-.sha256 hive-storage-X.Y.Z-binrcR.tar.gz.asc --detach-sig hive: OK % gpg hive-storage-X.Y.Z-binrcR.tar.gz

Copy release files to a public place.

No Format
% ssh people.apache.org mkdir public_html/hive-X.Y.Z-candidate-0 % scp -p hive.asc gpg: assuming signed data in `hive-storage-X.Y.Z-rcR.tar.gz people.apache.org:public_html/hive-X.Y.Z-candidate-0

Publish Maven artifacts to the Apache staging repository:

No Format
% ant -Dversion=X.Y.Z -Dmvn.publish.repo=staging maven-build % ant -Dversion=X.Y.Z -Dmvn.publish.repo=staging maven-publish

Login to the Apache Nexus server and "close" the staged repository. This makes the artifacts available at a temporary URL.

Voting

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:

http://people.apache.org/~you/hive-X.Y.Z-candidate-N

Maven artifacts are available here:

https://repository.apache.org/content/repositories/orgapachehive-121/

Source tag for RCN is at:
http://svn.apache.org/viewvc/hive/tags/release-X.Y.Z-RCN/

Voting will conclude in 72 hours.

Hive PMC Members: Please test and vote.

Thanks.

Verifying the release candidate

Verifying the PGP signature

No Format


#get the hive committers keys file
wget http://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

Verifying the md5 checksum
See the step under building

Publishing

Once three PMC members have voted for a release, it may be published.

'
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>"

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

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

Publishing the Storage API Artifacts

After the release vote passes, push the artifacts to Nexus. (If you get an error gpg: signing failed: Inappropriate ioctl for device trying doing export GPG_TTY=$(tty) .)
No Format
% git checkout storage-release-X.Y.Z-rcR % cd storage-api % mvn -Papache-release -DskipTests clean deploy
Login to Nexus and close the repository. Mark the repository as released.

Create the final tag (be very careful, tags in "rel/" are not changeable).

No Format
% git checkout storage-release-X.Y.Z-rcR % git tag -s rel/storage-release-X.Y.Z -m "Hive Storage API X.Y.Z" % git push origin rel/storage-release-X.Y.Z

Add the artifacts to Hive's dist area. There might be a problem with the size of the artifact.
Jira
server ASF JIRA
serverId 5aa69414-a9e9-3523-82ec-879b028fb15b
key INFRA-23055
solved the issue.

No Format

% 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 https://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

Preparing Branch for further development

Edit storage-api/pom.xml to change version to X.Y.Z+1-SNAPSHOT.
Edit pom.xml to change storage-api.version to X.Y.Z+1-SNAPSHOT.
Commit the changes back

No Format
% git commit -a -s -m 'Preparing for development post-X.Y.Z.' % git push origin storage-branch-X.Y

Cleaning Up Storage API Artifacts

Delete the storage-release-X.Y.Z-rcR tags.
Delete the artifacts from home.apache.org.

Hive Release

Preparation

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).
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).
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 https://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).

Notify developers on the #hive IRC channel and dev@hive mailing lists that you are about to branch a release.

Create a branch for the release series:

Code Block

language	text

git checkout -b branch-X.Y origin/master
git push -u origin branch-X.Y

Increment the value of the version property in all pom.xml files. For example, if the current value is 0.7.0-SNAPSHOT, the new value should be 0.8.0-SNAPSHOT. Please note that the SNAPSHOT suffix is required in order to indicate that this is an unreleased development branch. This can be accomplished with a single command using Maven's Versions plugin as follows:
Code Block
language text
mvn versions:set -DnewVersion=X.Y.0-SNAPSHOT -DgenerateBackupPoms=false
Make changes to metastore upgrade scripts. See HIVE-6555 on how this was done for HIVE 0.13.
Verify that the build is working with changes.
Commit these changes to master with a comment "Preparing for X.Y+1.0 development".

Updating Release Branch

These operations take place in the release branch.

Check out the release branch with:

Code Block

language	text

git clone https://git-wip-us.apache.org/repos/asf/hive.git/ <hive_src_dir>
cd <hive_src_dir>
git checkout branch-X.Y

Update the version property value in all pom.xml files. You should remove the SNAPSHOT suffix and set version equal to hive-X.Y.Z where Z is the point release number in this release series (0 for the first one, in which case this step is a no-op since you already did this above when creating the branch). Use Maven's Versions plugin to do this as follows:
Code Block
language text
mvn versions:set -DnewVersion=0.7.0 -DgenerateBackupPoms=false
Make sure to update the version property in standalone-metastore/pom.xml and upgrade-acid/pom.xml.
Remove the storage-api from the list of modules to build in the top level pom.xml. Set the storage-api.version property to the release of storage-api that you are using for your release. Make sure to set the storage-api.version property in standalone-metastore/pom.xml as well.
Update the the value of the TRACKING_BRANCH field in the .reviewboardrc file to point to the origin/branch-X.Y.
Verify that the build is working with changes.
Commit these changes with a comment "Preparing for X.Y.Z release".
If not already done, merge desired patches from trunk into the branch and commit these changes. Avoid usage of "git merge" to avoid too many merge commits. Either request the committer who committed that patch in master to commit to this branch, or commit it yourself, or try doing a git cherry-pick for trivial patches. Specifics of this step can be laid down by the release manager.
You probably also want to commit a patch (on both trunk and branch) which updates README.txt to bring it up to date (at a minimum, search+replacing references to the version number). Also check NOTICE to see if anything needs to be updated for recent library dependency changes or additions.
1. Select all of the JIRAs for the current release that aren't FIXED and do bulk update to clear the 'Fixed Version' field.
2. Likewise, use JIRA's Release Notes link to generate content for the RELEASE_NOTES.txt file. Be sure to select 'Text' format. (It's OK to do this with a direct commit rather than a patch.)
3. Update the release notes in trunk with the release notes in branch.
Tag the release candidate (R is the release candidate number, and also starts from 0):
Code Block
language text
git tag -a release-X.Y.Z-rcR -m "Hive X.Y.Z-rcR release." git push origin release-X.Y.Z-rcR

Building

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

Build the release (binary and source versions) after running unit tests. Manually create the sha256 files.

No Format

% mvn install -Pdist,iceberg -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

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

Check that release file looks ok -- e.g., install it and run examples from tutorial.

Setup your PGP keys for signing the release, if you don't have them already.

See https://www.apache.org/dev/release-signing.html, https://www.apache.org/dev/openpgp.html.

No Format

% gpg --full-generate-key
% gpg --keyserver hkp://keyserver.ubuntu.com --send-keys <PUB_KEY>
% svn co --depth files https://dist.apache.org/repos/dist/release/hive
% cd hive
% (gpg --list-sigs <NAME> && gpg --armor --export <NAME>) >> KEYS
% svn add KEYS
% svn commit -m 'Adding <FullName>'s key'

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

Follow instructions in https://www.apache.org/dev/release-publishing.html#distribution to push the new release artifacts (tar.gz, tar.gz.asc, tar.gz.sha256) to the SVN staging area of the project (https://dist.apache.org/repos/dist/dev/hive/). Make sure to create a new directory for the release candidate. You may need PMC privileges to do this step – if you do not have such privileges, please ping a PMC member to do this for you.

No Format

svn co --depth empty https://dist.apache.org/repos/dist
cd dist

svn update --set-depth empty dev
svn update --set-depth empty dev/hive
mkdir dev/hive/rX.Y.Z/

cp <hive-source-dir>/packaging/target/apache-hive-X.Y.Z*.tar.gz* dev/hive/r.X.Y.Z/
svn add dev/hive/rX.Y.Z
svn commit -m "Hive X.Y.Z release"

Publish Maven artifacts to the Apache staging repository. Make sure to have this setup for Apache releases. Use committer setting.xml.
Note: If you get an error gpg: signing failed: Inappropriate ioctl for device, try doing `export GPG_TTY=$(tty)`
Note: if you have multiple gpg keys, you may need to specify which key to use via -Dgpg.keyname=<PRIV_KEY>
No Format
% mvn deploy -DskipTests -Papache-release,iceberg -Dmaven.javadoc.skip=true
Login to the Apache Nexus server and "close" the staged repository. This makes the artifacts available at a temporary URL.

Voting

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:

https://people.apache.org/~you/hive-X.Y.Z-candidate-N

The checksums are these:
- ff60286044d2f3faa8ad1475132cdcecf4ce9ed8faf1ed4e56a6753ebc3ab585  apache-hive-4.0.0-alpha-1-bin.tar.gz
- 07f30371df5f624352fa1d0fa50fd981a4dec6d4311bb340bace5dd7247d3015  apache-hive-4.0.0-alpha-1-src.tar.gz

Maven artifacts are available here:

https://repository.apache.org/content/repositories/orgapachehive-121/

The tag release-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-rcR

The git commit hash is:

https://github.com/apache/hive/commit/357d4906f5c806d585fd84db57cf296e12e6049b 

Voting will conclude in 72 hours.

Hive PMC Members: Please test and vote.

Thanks.

Verifying the Release Candidate

Verifying the PGP signature:

No Format

#get the hive committers keys file
wget https://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

Verifying the sha256 checksum:
See the step under Building.

Publishing

Once three PMC members have voted for a release, it may be published.

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

Move the release artifacts to the release area of the project (https://dist.apache.org/repos/dist/release/hive/). Using svn mv command is important otherwise you may hit size limitations applying to artifacts(
Jira
server ASF JIRA
serverId 5aa69414-a9e9-3523-82ec-879b028fb15b
key INFRA-23055
)
No Format
svn mv https://dist.apache.org/repos/dist/dev/hive/hive-X.Y.Z https://dist.apache.org/repos/dist/release/hive/hive-X.Y.Z -m "Move hive-X.Y.Z release from dev to release"
Wait till the release propagates to the mirrors and appears under: https://dlcdn.apache.org/hive/
In your base hive source directory, generate javadocs as follows:
No Format
mvn clean install javadoc:javadoc javadoc:aggregate -DskipTests -Pjavadoc
After you run this, you should have javadocs present in your <hive_source_dir>/target/site/apidocs

Check out the javadocs svn repository as follows:

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

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)

Prepare to edit the website.

No Format
git clone https://github.com/apache/hive-site.git

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

./downloads.md:### 18 May 2015 : release 1.2.0 available
./downloads.md:You can look at the complete [JIRA change log for this release][HIVE_1_2_0_CL].
./downloads.md:[HIVE_1_2_0_CL]: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329345&styleName=Text&projectId=12310843
./javadoc.md:  * [Hive 1.2.0 Javadocs][r1.2.0]
./javadoc.md:[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.

Push your changes to the https://github.com/apache/hive-site/tree/gh-pages branch, and you can preview the results at https://apache.github.io/hive-site/. If everything is ok, then you can push your changes to https://github.com/apache/hive-site/tree/main branch and see the results at https://hive.apache.org/ site.
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 releases page. Select the version number you are releasing, and hit the release button. 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.
Login to the Apache Nexus server and mark the release candidate artifacts as released.
Add the release in Apache Committee Report Helper for the next board report to pick that up automatically.

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
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. (MapReduce is deprecated, and Spark has been removed so the text needs to be modified depending on the release version)

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

Preparing Branch for Future Maintenance Release

After the release has been completed, prepare the branch for the next development cycle.

Check out the release branch with:

Code Block

language	text

git clone https://git-wip-us.apache.org/repos/asf/hive.git/ <hive_src_dir>
cd <hive_src_dir>
git checkout branch-X.Y

Increment the version property value in all pom.xml files and add the SNAPSHOT suffix. For example, if the released version was 0.7.0, the new value should be 0.7.1-SNAPSHOT. Please note that the SNAPSHOT suffix is required in order to indicate that this is an unreleased development branch. Use Maven's Versions plugin to do this as follows:
Code Block
language text
mvn versions:set -DnewVersion=0.7.1-SNAPSHOT -DgenerateBackupPoms=false
If the release number you are preparing moves the major (first) or minor (second) number, update the Hive version name in the poms. In both pom.xml and standalone-metastore/pom.xml search for the property hive.version.shortname. This should match the new version number.
For example, if you are working on branch-3 and have just released Hive 3.2 and are preparing the branch for Hive 3.3 development, you need to update both poms to have <hive.version.shortname>3.3.0</hive.shortname.version>. If however you are working on branch-3.1 and have just released Hive 3.1.2 and are preparing the branch for 3.1.3 development, this is not necessary.
Verify that the build is working with changes.
Commit these changes with a comment "Preparing for X.Y.Z+1 development".

Tag the release:

No Format
svn move https://svn.apache.org/repos/asf/hive/tags/release-X.Y.Z-rcR \ https://svn.apache.org/repos/asf/hive/tags/release-X.Y.Z -m "HiveX.Y.Z release."

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

No Format
ssh people.apache.org cp -pR public_html/hive-X.Y.Z-candidate-0/ /www/www.apache.org/dist/hive/hive-X.Y.Z cd /www/www.apache.org/dist/hive chgrp -R hive hive-X.Y.Z chmod -R g+w hive-X.Y.Z

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.
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
Wait 24 hours for release to propagate to mirrors.

Prepare to edit the website.

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

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 the documentation for the obsoleted release.
Code Block
svn rm publish/docs/rX.Y.Z-1
Update the documentation links in author/src/documentation/content/xdocs/site.xml.
Update the release news in author/src/documentation/content/xdocs/releases.xml.
Update publish/.htaccess with the current release and any new redirects for obsoleted releases.

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

Code Block
ant -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."

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.
Login to the Apache Nexus server and mark the release candidate artifacts as released.
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 MapReduce For Hive release details and downloads, please visit: http://hive.apache.org/releases.html Hive X.Y.Z Release Notes are available here: 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

Space shortcuts

Child pages

Versions Compared

Old Version 27

New Version Current

Key

Preparation

Branching

Table of Contents

Storage API Release

Storage API Prepare Master Branch

Updating Release Branch

Storage API Branching

Making Storage API Release Artifacts

Building

Voting

Verifying the release candidate

Publishing

Publishing the Storage API Artifacts

Preparing Branch for further development

Cleaning Up Storage API Artifacts

Hive Release

Preparation

Branching

Updating Release Branch

Building

Voting

Verifying the Release Candidate

Publishing

Preparing Branch for Future Maintenance Release

See Also