Page History

...

Please refer "Preparing a release" section in http://plc4x.apache.org/developers/release.html to see what actually happens with the command below - has a good explanation along with screenshots, our gitbox url for checking is https://gitbox.apache.org/repos/asf?p=incubator-pinot.git) 

Before executing the step below, this page is a useful read these pages:

...

You can also verify from https://github.com/apache/incubator-pinot that a new tag has appeared , and that the commit of the pom files shows up.

...

You will need to cut-paste the release notes you prepared in the earlier steps. (DO NOT list the entire commit log for release notes).

1. Pull up the site https://github.com/apache/incubator-pinot/releases/
2. The new tag created during the release-preparation step above will automatically show up on the page. Click "Draft a new release" button, put "tag version" as the one you used from the previous step (e.g. release-0.3.0-rc2). Change the branch field to your release branch.
3. Fill in the release note (cut/paste)
4. Be sure to check the "This is a pre-release" box.
5. Publish the release.

...

# Commit the files to staging svn repository
$ cd /path/to/pinot-dev-dist
$ svn add apache-pinot-incubating-$VERSION-rc$RC
$ svn commit -m "Update apache-pinot-incubating-$VERSION-rc$RC"

Check https://dist.apache.org/repos/dist/dev/incubator/pinot/ to see if the files are uploaded correctly. requires -src/bin.tar.gz, tar.gz.asc, tar.gz.sha512 files.

...

1. Delete git repo release draft: https://github.com/apache/incubator-pinot/releases
2. Delete the maven artifacts. Log in to Nexus, select the staging repository (orgapachepinot-<number>) and click Drop button.

3. Clean up tarballs from dev dist

   Code Block
   language bash
   $ svn rm https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-$VERSION-rc$RC -m "Delete release-$VERSION-rc$RC" # NOTE: You will need your apache login and password for this step.

   
   

...

1. Move staging tarballs to the svn directory for official release 

   Code Block
   language bash
   $ svn mv https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-$VERSION-rc$RC https://dist.apache.org/repos/dist/release/incubator/pinot/apache-pinot-incubating-$VERSION # NOTE: You will need your apache login and password for this step.

   Check https://downloads.apache.org/incubator/pinot
   After several hours later, check http://www.apache.org/dyn/closer.cgi/incubator/pinot/apache-pinot-incubating-<version> to see if it shows up.
   (e.g. http://www.apache.org/dyn/closer.cgi/incubator/pinot/apache-pinot-incubating-0.7.1)

2. Delete release branch from github repo if any

   Code Block
   language bash
   $ git push origin --delete release-$VERSION

   
   

3. Update git tag for official release

   Code Block
   language bash
   $ git checkout tags/release-$VERSION-rc$RC $ git tag release-$VERSION -m "Apache Pinot (Incubating) $VERSION" $ git push origin release-$VERSION

   
   

4. Update Release note for the official release on Github https://github.com/apache/incubator-pinot/releases

   1. No need to draft a new release, just EDIT the previously drafted release

   2. Replace tag name to release-<version> tag

   3. Uncheck the pre-release checkbox, then publish

   4. Delete all other rc drafts if there is any.

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

   
   

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

...