Hi All, A patch release is being planned for Apache MXNet(incubating) to include some important bug fixes. I want to confirm that for a patch release, there is no RC and voting step.
Effectively the process looks something like this - Step 1: Cherrypick all the necessary bugfixes into the existing release branch. Step 2: Add a PR to update the version number etc (Example https://github.com/apache/incubator-mxnet/commit/e0c7906693f0c79b0ce34a4d777c26a6bf1903c1 ) Step 3: Make sure the release branch build passes on builds.apache.jenkins and nightly tests Step 4: tag the release branch in GitHub with the release tag - example 0.12.1 Step 5: Download from the repo and checkout the tag, package it and Sign the src code into 'apache-mxnet-src-0.12.1-incubating' Step 6: Validate the signatures and test Step 7: Update the website. (pip and docker release) Step 8: Upload the src tar to the final destination - http://www.apache.org/dist/incubator/mxnet/ Step 9: Announce the patch release Thanks, Meghna Baijal