...

• Enter Apache Nexus and do the following:
  

  1. Click on Log In in the upper right corner. Log in using your apache user name and password.  

  2. In the left navigation pane, select Staging Repositories.  

  3. 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.)  

  4. Click the Close button above the Repository names. This makes your release candidate available at the Staging level.  

  5. 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.  

  6. 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 (old procedure)

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.

# 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 *-bin.tar.gz
put *-bin.tar.gz.asc
put *-bin.tar.gz.sha512
lcd ../../target

# pwd should be target/checkout/target
put *.tar.gz
put *.tar.gz.asc
put *.tar.gz.sha512

# uplading website (sftp needs directory tree to be pre-created?)
lcd ../zookeeper-docs/target/html
mkdir website
mkdir website/images
mkdir website/skin
cd website
put -r * 

Stage source and binaries to Apache dev repo

Copy release files to a public place and ensure they are readable. 

# Staged artifacts built by "release:perform" are in target/checkout

ZKHOME=where you have your work directory "zookeeper"
svn co https://dist.apache.org/repos/dist/dev/zookeeper/ zookeeper_dev
cd zookeeper_dev
mkdir zookeeper-$VERSION-candidate-0
cd zookeeper-$VERSION-candidate-0


cp $ZKHOME/target/checkout/zookeeper-assembly/target/*.tar.gz* .

mkdir website
cp -r $ZKHOME/target/checkout/zookeeper-docs/target/html .

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.6.0 candidate 0   This is a release candidate for 3.6.0. It is a major release and it introduces a lot of new features, most notably: - Built-in data consistency check inside ZooKeeper - Allow Followers to host Observers - A new feature proposal to ZooKeeper: authentication enforcement - Pluggable metrics system for ZooKeeper (and Prometheus.io integration) - TLS Port unification - Audit logging in ZooKeeper servers - Improve resilience to network (advertise multiple addresses for members of a Zookeeper cluster) - Persistent Recursive Watch - add an API and the corresponding CLI to get total count of recursive sub nodes under a specific path   The full release notes is available at:   https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801&version=12346617   *** Please download, test and vote by January 19th 2020, 23:59 UTC+0. ***   Source files: https://people.apache.org/~eolivelli/zookeeper-3.6.0-candidate-0/   Maven staging repo: https://repository.apache.org/content/repositories/orgapachezookeeper-1045/   The release candidate tag in git to be voted upon: release-3.6.0-0 https://github.com/apache/zookeeper/tree/release-3.6.0-0   ZooKeeper's KEYS file containing PGP keys we use to sign the release: https://www.apache.org/dist/zookeeper/KEYS Please note that this new major release introduces these change in the staging area: - the source artifacts package is in zip format - we are releasing a new binary package with the C client (with OpenSSL support) - website preview We are also adding a new JAR: zookeeper-metrics-providers The staging version of the website is: https://people.apache.org/~eolivelli/zookeeper-3.6.0-candidate-0/website/ Should we release this candidate? Release Manager Signature

  
  

...

• Enter Apache Nexus and do the following:
  

  1. Click on Log In in the upper right corner. Log in using your apache user name and password.  

  2. In the left navigation pane, select Staging Repositories.  

  3. 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.)  

  4. Click the Close button above the Repository names. This makes your release candidate available at the Staging level.  

  5. 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.  

  6. 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.

...