...

In case you have to run more than one RC you have to update the release notes every time and push them to those two branches.

Please make sure that the entire history of the actual release linue is present in the release notes. For example in case of release 3.6.3, the notes from 3.6.0 to 3.6.3 are included.

Build and check that the release branch is in good shape

...

Preparing the release candidate (prepare stage artifacts for VOTE)

• Using dUsing the same directory in which you run "release:prepare" perform these are steps

  • Maven Release Plugin uses release.properties files prepared by release:prepare

  • It checks out a new copy of the repository at gitsha pointed by $TAG (like release-3.6.0-0) inside zookeeper/target/checkout

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

  Code Block
  mvn release:perform -Darguments='-DskipTests=true -Papache-release' -Papache-release

  
  

• You should have the SIGNED jar files and also the tarballs built. The two tarball is available at:
  • target/checkout/zookeeper-assembly/target/apache-zookeeper-X.Y.Z-bin.tar.gz
  • target/checkout/target/apache-zookeeper-X.Y.Z-source-release.tar.gz
• This command also staged all of the maven artifacts to repository.apache.org

...