Page History

...

• Build the projects with maven (we are skipping runit the unit tests here, but you should run them at least once on the release branch before continuing)

• 
  

  Ensure that you are using JDK8 and Maven 3.6+

• There is no need to build the C client or "contrib" packages

  Code Block
  mvn -v mvn clean install -DskipTests

  
  

• You should have the jar files and also the tarballs built. The two tarball is available at:
  • zookeeper-assembly/target/apache-zookeeper-X.Y.Z-bin.tar.gz
  • zookeeper-assembly/target/apache-zookeeper-X.Y.Z.tar.gz

• Sign the tarballs:

  Code Block
  cd zookeeper-assembly/target gpg --armor --output apache-zookeeper-$VERSION-bin.tar.gz.asc --detach-sig apache-zookeeper-$VERSION-bin.tar.gz gpg --armor --output apache-zookeeper-$VERSION.tar.gz.asc --detach-sig apache-zookeeper-$VERSION.tar.gz

  
  

• Check that release file looks ok - e.g. install it and run examples from tutorial.
  • untar the release artifact in a test directory

  • try to build the sources with

    Code Block
    mvn clean install -DskipTests -Pfull-build

    
    

• 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-X.Y.Z-candidate-0 > cd zookeeper-X.Y.Z-candidate-0 > put zookeeper-X.Y.Z.tar.gz* > bye

  
  

• Deploy to the Maven Repository.
  This is done using apache-release profile, coming from the apache parent pom. This will also sign your artifacts if your settings.xml is configured as mentioned above.
  The following command copies all artifacts to a temporary staging Apache mvn repository in open state:
  

  Code Block
  mvn deploy -DskipTests -Papache-release

  
  

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

• 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 that affect 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: http://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: http://www.apache.org/dist/zookeeper/KEYS   Should we release this candidate?

  
  

...