...
Move staging tarballs to the svn directory for official release
Code Block language bash $ svn mv https://dist.apache.org/repos/dist/dev/pinot/apache-pinot-$VERSION-rc$RC https://dist.apache.org/repos/dist/release/pinot/apache-pinot-$VERSION # NOTE: You will need your apache login and password for this step.
Check https://downloads.apache.org/pinot
After several hours later, check http://www.apache.org/dyn/closer.cgi/pinot/apache-pinot-<version> to see if it shows up.
(e.g. http://www.apache.org/dyn/closer.cgi/pinot/apache-pinot-0.8.0)Delete previous release tarballs
We only need to keep the most recent release, so feel free to delete any previous released distributions.
Code Block language bash $ svn rm https://dist.apache.org/repos/dist/release/pinot/apache-pinot-0.8.0 # NOTE: You will need your apache login and password for this step.Delete release branch from github repo if any
Code Block language bash $ git push origin --delete release-$VERSION-rc
Update git tag for official release
Code Block language bash $ git checkout tags/release-$VERSION-rc$RC $ git tag release-$VERSION -m "Apache Pinot $VERSION" $ git push origin release-$VERSION
Update Release note for the official release on Github https://github.com/apache/pinot/releases
No need to draft a new release, just EDIT the previously drafted release
Replace tag name to release-<version> tag
Uncheck the pre-release checkbox, then publish
- Delete all other rc drafts if there is any.
Delete all RC tags from github repo
Code Block language bash # Clean up the rc tag to not to show on the Github release page $ git tag -d release-$VERSION-rc$RC $ git push origin :refs/tags/release-$VERSION-rc$RC
- Publish the maven artifacts. Log in to Nexus, select the staging repository (orgapachepinot-<number>) and click Release button. Several hours later, the new version should show up at https://repo.maven.apache.org/maven2/org/apache/pinot
...