Preliminaries

Apache Release Documentation

Code Signing Key

Create a code signing gpg key for release signing; use <your Apache ID>@apache.org for your primary ID for the code signing key. See the Apache Release Signing documentation for further information.

Add your code signing key to your Apache ID here
Publish it to a public key server such as the MIT key server.
Add it to the HAWQ KEYS file.

Ensure JIRA Issues are Appropriately Tagged for the Release

Ensure that all HAWQ JIRA issues that are addressed in this release are marked with the release version in the ‘FixVersion’ field of the issue.

Create the Release Candidate

Prepare Tarballs

Tag your release: (or create a release branch)
git tag -a <tag name> <commit SHA> -m "<message for the tag>"

push to origin:
git push origin <tag name> -m "<tag description message>"

Make a tarball and gzip:

git archive -o ../apache-hawq-src-<your release name>.tar --prefix=apache-hawq-src-<your release name>/ <your tag/branch name>
gzip ../apache-hawq-src-<your release name>.tar

Example:

$ git archive -o ../apache-hawq-src-2.1.0.0-incubating.tar --prefix=apache-hawq-src-2.1.0.0-incubating/ 2.1.0.0-incubating
$ gzip ../apache-hawq-src-2.1.0.0-incubating.tar

Prepare MD5, SHA256 and ASC files from the source tarball:

md5 apache-hawq-src-<your release name>.tar.gz > apache-hawq-src-<your release name>.tar.gz.md5
shasum -a 256 apache-hawq-src-<your release name>.tar.gz > apache-hawq-src-<your release name>.tar.gz.sha256 
gpg --detach-sign -a apache-hawq-src-<your release name>.tar.gz

Example:

$ md5 apache-hawq-src-2.1.0.0-incubating.tar.gz > apache-hawq-src-2.1.0.0-incubating.tar.gz.md5
$ shasum -a 256 apache-hawq-src-2.1.0.0-incubating.tar.gz > apache-hawq-src-2.1.0.0-incubating.tar.gz.sha256
$ gpg --detach-sign -a apache-hawq-src-2.1.0.0-incubating.tar.gz

You need a passphrase to unlock the secret key for
user: "Edward Bartolo Espino (CODE SIGNING KEY) <espino@apache.org>"
4096-bit RSA key, ID 57325522, created 2017-01-09

$ ls -al apache-hawq-src-2.1.0.0-incubating*

-rw-r--r-- 1 espino staff 35214063 Jan 10 11:04 apache-hawq-src-2.1.0.0-incubating.tar.gz
-rw-r--r-- 1 espino staff 819 Jan 10 11:09 apache-hawq-src-2.1.0.0-incubating.tar.gz.asc
-rw-r--r-- 1 espino staff 83 Jan 10 11:10 apache-hawq-src-2.1.0.0-incubating.tar.gz.md5
-rw-r--r-- 1 espino staff 84 Jan 10 11:10 apache-hawq-src-2.1.0.0-incubating.tar.gz.sha256

Retrieve the subversion dev incubator hawq repo
Example: svn checkout https://dist.apache.org/repos/dist/dev/incubator/hawq/ --username=<your apache user>
Create a local folder for the release (e.g. 2.0.0.0-incubating.RC1) in svn. We use apache's distribution repo: https://dist.apache.org/repos/dist/dev/incubator/hawq/
Move the files into the release folder on local disk.
svn add <release folder>
Commit artifacts:
Example: svn commit -m 'adding 2.0.0.0-incubating RC1 candidate release artifacts' --username=<your apache user id>

Validate the Release Candidate

As per the Apache documentation, verify that the release candidate artifacts satisfy the following:

Checksums and PGP signatures are valid
Build is successful
DISCLAIMER is correct, filenames include “incubating”
LICENSE and NOTICE files are correct and dependency licenses are acceptable
- LICENSE and NOTICE files at the root of the artifact directory must only reflect the contents of the artifact in which they are contained.
- See:
  - LICENSE file requirements
  - LICENSE requirements for distribution artifacts with multiple licenses
  - NOTICE file requirements
  - Apache Legal
  - Acceptable and Unacceptable Dependency Licenses
All source files have license headers where appropriate, RAT checks pass
The provenance of all source files is clear (ASF or software grants)

Vote on the Release

As per the Apache Incubator release guidelines, all releases for incubating projects must go through a two-step voting process. First, release voting must successfully pass within the Apache HAWQ community via the dev@hawq.incubator.apache.org mailing list. Then, release voting must successfully pass within the Apache Incubator PMC via the general@incubator.apache.org mailing list.

General information regarding the Apache voting process can be found here.[

Apache HAWQ Community Vote

To vote on a candidate release, send an email to the dev list with subject: [VOTE]: Apache HAWQ <release version> Release and a body along the lines of:

This is the vote for <release version> of Apache HAWQ (incubating).

The vote will run for at least 72 hours and will close on <closing date>.

The artifacts can be downloaded here: https://dist.apache.org/repos/dist/dev/incubator/HAWQ/release/<release number>

All JIRAs completed for this release are tagged with 'FixVersion = <release version>'. You can view them here: <insert link to the JIRA release notes>

The artifacts have been signed with Key : <ID of signing key>

Please vote accordingly:
[ ] +1, accept RC as the official <release version> release 
[ ] -1, do not accept RC as the official <release version> release because...

If any -1 (binding) votes are entered, then address them such that the voter changes their vote to a +1 (binding) or cancel the vote, fix the issues, and start over with Prepare Tarballs.

Once 72 hours has passed (which is generally preferred) and/or at least three +1 (binding) votes have been cast with no -1 (binding) votes, send an email closing the vote and pronouncing the release candidate a success. Please use the subject: [RESULT][VOTE]: Apache HAWQ <release version> Release.

The Apache HAWQ <release version> vote is now closed and has passed as follows:

[number] +1 (binding) votes
[number] -1 (binding) votes

A vote Apache HAWQ <release version> will now be called on general@incubator.apache.org.

Incubator PMC Vote

Once the candidate release vote passes on dev@hawq.apache.incubator.org, call a vote on IMPC general@incubator.apache.org with an email a with subject: [VOTE]: Apache HAWQ <release version> Release and a body along the lines of:

The PPMC vote for the Apache HAWQ <release version> release has passed. We kindly request that the IPMC now vote on the release.

The PPMC vote thread is located here: <link to the dev voting thread>

The artifacts can be downloaded here: https://dist.apache.org/repos/dist/dev/incubator/hawq/release/<release number> 

The artifacts have been signed with Key : <ID of signing key>

All JIRAs completed for this release are tagged with 'FixVersion = <release version>'. You can view them here: <insert link to the JIRA release notes>

Please vote accordingly:

[ ] +1, accept as the official Apache HAWQ <release number> release 
[ ] -1, do not accept as the official Apache HAWQ <release number> release because...

The vote will run for at least 72 hours.

If any -1 (binding) votes are entered, then address them such that the voter changes their vote to a +1 (binding) or cancel the vote, fix the issues, and start over with Prepare Tarballs (including re-voting within the Apache HAWQ community on dev@hawq.apache.incubator.org).

Once 72 hours has passed (which is generally preferred) and/or at least three +1 (binding) votes have been cast with no -1 (binding) votes, send an email closing the vote and pronouncing the release candidate a success. Please use the subject: [RESULT][VOTE]: Apache HAWQ <release version> Release

The Apache HAWQ <release version> vote is now closed and has passed as follows:

[number] +1 (binding) votes
[number] -1 (binding) votes

The Apache HAWQ (incubating) community will proceed with the release.

Publishing and Distributing Release

Finalizing your tag
switching to master branch

git tag -s rel/v{version} <commit SHA> -m "Apache HAWQ(incubating) {version) release (<other comments>)"

Sign your release tag

You need to configure your git user signing key first before you can sign a tag.

git config --global user.signingkey <Your secret key SHA>

Push your tag to remote (origin)
```
git push origin rel/v{version}
 
```
Move tarballs from staging folder to release location:
```
svn mv https://dist.apache.org/dist/dev/incubator/hawq/{version}.RC#/ https://dist.apache.org/dist/release/incubator/hawq/{version}
```
Commit Message

As if you put https URL in svn commands, it'll commit automatically. A text editor will popup for you to edit commit message, put something like: "Release Apache HAWQ (incubating) {{version}}"
Add download link on hawq website: http://hawq.apache.org/
Go to http://issues.apache.org/jira/browse/hawq to release the specific version (need admin permission , under "Version")

Announce the Release

Send an email to announce@apache.org, general@incubator.apache.org, and dev@hawq.apache.incubator.org with the subject: [ANNOUNCE] Apache HAWQ <release number> Release and a body along the lines of:

Apache HAWQ (incubating) Project Team is proud to announce Apache
HAWQ <release version> has been released.

Apache HAWQ (incubating) combines exceptional MPP-based analytics
performance, robust ANSI SQL compliance, Hadoop ecosystem
integration and manageability, and flexible data-store format
support, all natively in Hadoop, no connectors required. Built
from a decade’s worth of massively parallel processing (MPP)
expertise developed through the creation of the Pivotal
Greenplum® enterprise database and open source PostgreSQL, HAWQ
enables to you to swiftly and interactively query Hadoop data,
natively via HDFS.

*Download Link*:
https://dist.apache.org/repos/dist/release/incubator/hawq/<release version>/

*About this release*
This is a source code only release

All changes:
https://cwiki.apache.org/confluence/display/HAWQ/HAWQ+Release+2.1.0.0-incubating+Release


*HAWQ Resources:*

   - JIRA: https://issues.apache.org/jira/browse/HAWQ
   - Wiki: https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+Home
   - Mailing list(s): dev@hawq.incubator.apache.org
                      user@hawq.incubator.apache.org

*Know more about HAWQ:*
http://hawq.apache.org

- Apache HAWQ (incubating) Team

=====
*Disclaimer*

Apache HAWQ (incubating) is an effort undergoing incubation at The
Apache Software Foundation (ASF), sponsored by the name of Apache
Incubator PMC. Incubation is required of all newly accepted
projects until a further review indicates that the
infrastructure, communications, and decision making process have
stabilized in a manner consistent with other successful ASF
projects. While incubation status is not necessarily a reflection
of the completeness or stability of the code, it does indicate
that the project has yet to be fully endorsed by the ASF.

General Apache information regarding announcing a release may be found here.

Space shortcuts

Page tree

Preliminaries

Apache Release Documentation

Code Signing Key

Ensure JIRA Issues are Appropriately Tagged for the Release

Create the Release Candidate

Prepare Tarballs

Validate the Release Candidate

Vote on the Release

Apache HAWQ Community Vote

Incubator PMC Vote

Publishing and Distributing Release

Announce the Release

Space shortcuts

Page tree

Release Process: Step by step guide

Preliminaries

Apache Release Documentation

Code Signing Key

Ensure JIRA Issues are Appropriately Tagged for the Release

Create the Release Candidate

Prepare Tarballs

Validate the Release Candidate

Vote on the Release

Apache HAWQ Community Vote

Incubator PMC Vote

Publishing and Distributing Release

Announce the Release