accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Corey J. Nolet (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3156) Document full release process
Date Fri, 26 Sep 2014 03:17:34 GMT


Corey J. Nolet commented on ACCUMULO-3156:

Update of my notes to include post-vote bullet points.

- Add the next version to JIRA.

- A PGP key needs to be made. GnuPGP is one way to do this. More details can be found on the
Apache Guide for New Committers.

- Once the key is made, you will need to use gpg-agent or something similar to cache your
key and credentials so that the maven gpg plugin can properly sign all the artifacts.

- You will need to add your gpg public key to the keys file:

Add your apache id and password for the necessary servers to your settings.xml. You should
use the following link to encrypt your password:

<!-- To publish a release -->

- Go to the "Road Map" in JIRA under the Accumulo project and click on "Release Notes" under
the unreleased version in question. Note that this will give you open tickets as well. One
way to do this is to look @ all the open tickets for the version and remove them manually
from the release notes. Depending on the type of release, it's possible now could be a good
time to move the versions of the JIRA tickets to the next unreleased bugfix for the major
version line you are releasing.

-Run the following commands to branch and release:

git co -b 1.6.2-SNAPSHOT

[19:44][cjnolet@coreys-mbp:/workspace/accumulo(1.6.2-SNAPSHOT)]$ git push -u origin 1.6.2-SNAPSHOT:1.6.2-SNAPSHOT
Total 0 (delta 0), reused 0 (delta 0)
 * [new branch]      1.6.2-SNAPSHOT -> 1.6.2-SNAPSHOT
Branch 1.6.2-SNAPSHOT set up to track remote branch 1.6.2-SNAPSHOT from origin.

mvn release:prepare 

mvn release:perform 

git co 1.6.1

git co -b 1.6.1-rc1

git push -u origin 1.6.1-rc1:1.6.1-rc1

- Fire off a message to the dev list with the following template:



Please consider the following candidate for Apache Accumulo 1.6.1

Branch: 1.6.1-rc1
SHA1: 88c5473b3b49d797d3dabebd12fe517e9b248ba2
Staging Repository:

Source tarball:
Binary tarball:
(Append ".sha1", ".md5" or ".asc" to download the signature/hash for a
given artifact.)

Signing keys available at:

Over 1.6.1, we have 188 issues resolved;a=blob;f=CHANGES;h=91b9d31e3b9dc53f1a576cc49bbc061919eb0070;hb=1.6.1-rc1

Testing: All unit and functional tests are passing. 

Vote will be open until Thursday, September 25th 12:00AM UTC (9/24 8:00PM ET, 9/24 5:00PM

- Once vote passes, release the artifacts in the staging repository.

- release the version in JIRA

- Remove old snapshot branch
git push -u origin :1.6.1-SNAPSHOT

- Create signed tag for released version from the RC branch and remove the RC branch

git tag -s 1.6.1 
git push --tags
git push -u origin :1.6.1-rc1
git co master
git merge 1.6.1

- Add tarballs to<version> along with their
associated ascii pgp (.asc). Also generate the MD5 and sha1 sums of the tarballs and place
them in their associated files. Remove the previous release in the current minor versioning
line (if releasing 1.6.1, remove the 1.6.0 directory).

- Change all jira tickets referencing released version to the next bugfix version

- Update the website 
   + Downloads page
   + apidocs
   + release notes
   + user manual

For API Docs:
svn checkout accumulo-site
cd accumulo-site
mkdir -p apidocs/1.6
cp -r <apidocs_location>/* apidocs/1.6
# remove apidocs/1.6 from extpaths.txt
svn add apidocs
svn add extpaths.txt
svn commit
# Go to CMS page and publish site to production. Wait for site to fully build and publish-
this will take awhile.
# add apidocs/1.6 to extpaths.txt
svn rm apidocs
svn commit

> Document full release process
> -----------------------------
>                 Key: ACCUMULO-3156
>                 URL:
>             Project: Accumulo
>          Issue Type: Task
>            Reporter: Corey J. Nolet
>            Assignee: Corey J. Nolet
> This should apply both to people who are familiar with the release process but want a
quick checklist or people who are new to the release process and have never done it before.

This message was sent by Atlassian JIRA

View raw message