THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- validate the contents of the staging Maven repository
Stage source and binaries to your own Apache home
Copy release files to a public place and ensure they are readable. Note that home.apache.org only supports SFTP, so this may be easier with a graphical SFTP client like Nautilus, Konqueror, etc.
| Code Block |
|---|
sftp home.apache.org
> cd public_html
> mkdir zookeeper-$VERSION-candidate-0
> cd zookeeper-$VERSION-candidate-0
> put zookeeper-$VERSION.tar.gz*
> bye
|
Close the Maven Repository
...
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.
...
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.
Close the Maven Repository
- 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.
Stage source and binaries to your own Apache home
Copy release files to a public place and ensure they are readable. Note that home.apache.org only supports SFTP, so this may be easier with a graphical SFTP client like Nautilus, Konqueror, etc.
| Code Block |
|---|
# Staged artifacts built by "release:perform" are in target/checkout
cd target/checkout/zookeeper-assembly/target
sftp home.apache.org
> cd public_html
> mkdir zookeeper-$VERSION-candidate-0
> cd zookeeper-$VERSION-candidate-0
> put *.tar.gz
> put *.tar.gz.asc
> put *.tar.gz.sha512
> bye
|
...
Call for VOTE
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):
Subject: [VOTE] Apache ZooKeeper release 3.4.6 candidate 0
This is a bugfix release candidate for 3.4.6. It fixes 117 issues, including issues thataffect leader election, Zab, and SASL authentication.
The full release notes is available at:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801&version=12323310
*** Please download, test and vote by March 9th 2014, 23:59 UTC+0. ***
Source files:https://people.apache.org/~fpj/zookeeper-3.4.6-candidate-0/
Maven staging repo:https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.4.6/
The release candidate tag in git to be voted upon: release-X.Y.Z-rcR
ZooKeeper's KEYS file containing PGP keys we use to sign the release:https://www.apache.org/dist/zookeeper/KEYS
Should we release this candidate?Release Manager Signature
...