Setting up the signing keys
Before you do a release you'll need a signing key that is registered with apache. If you already have one, you can skip this section. Otherwise, here are the steps to do:
- use gpg2 --gen-key to generate a new key. Make sure that the key size is 4096 bits, the key doesn't expire, and use CODE SIGNING KEY for the comment.
- Now you need to register your key at http://pgp.mit.edu/ using the output of gpg --armor --export <keyid>
- Add your key to the KEYS file:
- svn co https://dist.apache.org/repos/dist/release/zookeeper/ zookeeper_dist
- cd zookeeper_dist.
- edit the KEYS file. See the top of the KEYS file for instructions on how to edit this file
- svn ci
- Upload digest to your account on id.apache.org (gpg2 --fingerprint)
- when updating JIRA be sure to use the "batch change" operator under the "tools" menu. Disable email notifications when using batch change, subsequent to large JIRA operations (moving issues btw releases, closing JIRAs after a release, etc...) send email to the dev@ list detailing the changes.
Skip this section if this is NOT the first release in a series (i.e. release X.Y.0).
- Notify developers on the mailing list that you are about to branch a release.
- Update CHANGES.txt to include the release version and date (use Unreleased for the date if it is unknown) and remove Trunk (unreleased changes).
Commit these changes to trunk.
Create a branch for the release series:
- Update CHANGES.txt to add back in Trunk (unreleased changes).
- Update the default version in build.xml on trunk to X.Y+1.0-SNAPSHOT.
- Update the version number in src/c/configure.ac and src/c/include/zookeeper_version.h to be X.Y+1.0.
Commit these changes to trunk.
Updating the release branch
These operations take place in the release branch:
Check out the branch with:
git clone -b branch-X.Y https://git-wip-us.apache.org/repos/asf/zookeeper.git
If not already done, merge desired patches from trunk into the branch and commit these changes. You can find the revision numbers using svn log CHANGES.txt in the branch and in trunk.
- Do a final pass regeneration of docs by running "ant -Dforrest.home=<path to Forrest> clean docs". If there are any modifications, then they'll show up under the docs folder. If there are any changes, then commit them. However, DO NOT commit changes in docs/releasenotes.html or docs/releasenotes.pdf. (Release notes are handled in a separate step.) Release notes should be regenerated each time a documentation patch is committed. This final pass before the release is intended to catch mistakes in case this step was missed at commit time.
- Update CHANGES.txt to include the release version and date (this change must be committed to trunk and any intermediate branches between trunk and the branch being released).
Also, update CHANGES.txt with the committed jira details targeted for this release version. As we follow PR merging, jira info is not updated in this file while committing.
- Update docs/releasenotes.html with release notes for this release. You can get the HTML by following the "Release Notes" link for the relevant release on the https://issues.apache.org/jira/browse/ZOOKEEPER?report=com.sourcelabs.jira.plugin.portlet.releases:releases-projecttab#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel tab in Jira. Note that you need to exclude the won't fix or invalid tickets.
- TODO - document howto generate the release notes using the new mechanism
- Update the version number in build.xml to be ''X.Y.Z''
- Update the version number in src/c/include/winconfig.h, src/c/configure.ac, and src/c/include/zookeeper_version.h to be ''X.Y.Z''
- Update the copyright years in NOTICE.txt if it's outdated.
Commit these changes.git commit -a -m "Preparing for release X.Y.Z"git push <remote> <branch>
Tag the release candidate (R is the release candidate number, and starts from 0):git tag -s release-X.Y.Z-rcR -m "ZooKeeper X.Y.Z-rcR release."Push the newly created rc tag to the remote repo.git push <remote> release-X.Y.Z-rcR
Build the release & run unit tests.
- Untar the generated zookeeper-X.Y.Z.tar.gz and do the following:
Sign the toplevel zookeeper-X.Y.Z.jar
Sign each file in dist-maven
Tar/GZ the release directory as zookeeper-X.Y.Z.tar.gz
Generate the MD5/SHA1 checksums for the release artifact.
Sign the release
- Check that release file looks ok - e.g. install it and run examples from tutorial.
- untar the release artifact in a test directory
Copy release files to a public place.
- Stage the release artifacts to the Apache Nexus repository
Create ~/.m2/settings.xml introducing the values that are specific to you:
See http://maven.apache.org/guides/mini/guide-encryption.html for details on encrypting the passwords rather than leaving them in the clear.
Run the following on the branch check out
- Enter Apache Nexus and do the following:
Click on Log In in the upper right corner. Log in using your apache user name and password.
In the left navigation pane, select Staging Repositories.
- Identify the release candidate you just pushed, by your user name (in parentheses as part of the "Repository" name) and the "Created On" date. Click on the check box to the left of your Repository name to select it. (If you accidentally click on the Repository name itself, another tab will pop open. If so, just close it.)
Click the Close button above the Repository names. This makes your release candidate available at the Staging level.
If you have previously staged an older release candidate with the same version number, and it is still showing in the Repository list, you must select and Drop the old one now.
Confirm that your new release candidate is visible at https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/ with correct file modification dates.
Call for a release vote on dev (note dev@ and not user@, the user list is for discussion of released software only) at zookeeper.apache.org. Here is a sample email (from 3.4.6 release):
In the below release candidate dev mail format, we need to change the 'The tag to be voted upon:' section like,
"The RC tag in git to be voted upon: release-X.Y.Z-rcR"
Once three PMC members have voted for a release, it may be published.
Tag the release:git tag -s release-X.Y.Z -m "ZooKeeper X.Y.Z release."Push the newly created release tag to the remote repo.git push <remote> release-X.Y.Z
Update the version number to the next logical SNAPSHOT version (e.g. X.Y.Z to X.Y.Z+1-SNAPSHOT)
Check in release files to the distribution server
- After checking in the release, you'll receive an automated email from reporter.apache.org with a link requesting additional details about the release. This form must be completed by a PMC member. If you are a PMC members, follow the link and complete the form. If you are not a PMC member, forward the email to firstname.lastname@example.org and ask for assistance from a PMC member.
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.
- Release the Maven artifacts on Apache Nexus:
- Click on 'Staging repositories'.
- Select the repository corresponding to the release candidate.
- Click on the 'Release' button and follow instructions.
- Wait 24 hours for release to propagate to mirrors.
Prepare to edit the website.
Copy the new release documentation into the content/doc directory
- Update the release news in site/trunk/content/releases.textile
- Update the nav panel to include X.Y.Z (which may now be "current") site/trunk/templates/sidenav.textile
Regenerate the site, review it, then commit it. (checkout https://svn.apache.org/repos/infra/websites/cms/build if you haven't already)
Update the "current" doc pointer if necessary (as CMS doesn't currently support symlinks in build/staging we need to push this directly to production)
- Review your changes on the staging site: http://zookeeper.staging.apache.org
Deploy your site changes.
Send announcements to the user and developer lists once the site changes are visible. Here is a sample email:
- In Jira, ensure that only issues in the "Fixed" state have a "Fix Version" set to release X.Y.Z.
- In Jira, "release" the version. Visit the "Administer Project" page, then the "Manage versions" page. You need to have the "Admin" role in ZooKeeper's Jira for this step and the next.
- In Jira, close issues resolved in the release. Disable mail notifications for this bulk change.
Support is now available for pushing the jar artifacts to the Apache maven repository.
WARNING: the process has changed but the docs not yet updated, see https://issues.apache.org/jira/browse/ZOOKEEPER-1430
- login to people.apache.org
- copy the files from the release artifact "dist-maven" directory into /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/zookeeper/zookeeper/X.Y.Z
- chmod -R g+w /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/zookeeper/zookeeper/X.Y.Z
- cd to /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/zookeeper/zookeeper
- edit maven-metadata.xml
- add X.Y.Z to versions
- update the version to X.Y.Z
- update the lastUpdated
sign and md5sum maven-metadata.xml
Before the release, run the following smoke tests (at least).
- Run unit tests on different hardwares: mac, windows, linux.