Page History

...

1. The release candidate should contain all planned features, bug fixes, and code changes above. The release candidate commit should have passed the merge build, pip builds, nightly tests. Docs should also be manually built locally & checked for correctness. TODO: how to retrieve the commit hash.
2. Tag release candidate and export source package

• • Go to the GitHub repo’s “releases” tab
  • Click “Draft a new release”

1. • Provide the release tag in the form of “v#.#.#.rc0” where 0 means it’s the first release candidate
   • Select the commit by clicking Target: master > Recent commits > $commit_hash
   • Copy and paste NEWS change into the description box
   • Select “This is a pre-release"Source packages will be created. Download the .tar.gz to name it "apache-mxnet-src-#.#.#.rc0-incubating.tar.gz"
2. Create remaing artifacts for the release and push to the dist folder
   • apache-mxnet-src-#.#.#.rc0-incubating.tar.gz.asc: Create OpenGPG compatible ASCII armored detached signature http://www.apache.org/dev/release-signing.html#openpgp-ascii-detach-sig
   • apache-mxnet-src-#.#.#.rc0-incubating.tar.gz.md5: Create MD5 checksum
     • $ md5 apache-mxnet-src-#.#.#.rc0-incubating.tar.gz > apache-mxnet-src-#.#.#.rc0-incubating.tar.gz.md5
   • apache-mxnet-src-#.#.#.rc0-incubating.tar.gz.sha512: Create SHA checksum
     • $ shasum -a 512 apache-mxnet-src-#.#.#.rc0-incubating.tar.gz > apache-mxnet-src-#.#.#.rc0-incubating.tar.gz.sha512
   • KEYS: Add your public signing key to the dist folder
   • #.#.#-incubating.RC0 folder: Create a folder for this RC in the dist folder

...