...

3. Finalizing and posting a release

3.1. Marking & Publishing the Official release

Once the release candidate passes the vote, we draft the official release on GitHub and rename the release candidate as the official release.

Step 3.1.1: Draft official release on GitHub

...

• Go to the GitHub repo’s “releases” tab
• Click “Draft a new release”
• Provide the release tag in the form of
“0
• “<major>.
12
• <minor>.
0”
• <patch>”
• Select the commit by clicking Target: master > the passing release candidate tag
• Copy and paste NEWS change into the description box

Step 3.1.2: Rename and publish the source package

...

First upload to dev and then move to releases as

...

follows:

#create

...

a

...

directory

...

under

...

releases

...

-

...

https://httpd.apache.org/dev/release.html

This process needs to change -> http://www.apache.org/dev/release-download-pages.html

Code Block
language bash theme Midnight title Rename and Resign the RC to create GA linenumbers true
# Step 1: Download and Untar tar -zxvf apache-mxnet-src-0.11.0.rc3-incubating.tar.gz # Step 2: rename (remove the rc) and tar again mv apache-mxnet-src-0.11.0.rc3-incubating apache-mxnet-src-0.11.0-incubating gtar -czvf apache-mxnet-src-0.11.0-incubating.tar.gz apache-mxnet-src-0.11.0-incubating # Step 3: Resign now   # Step 4: First upload here - svn mv https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.11.0/   # Step 5: Move from dev to release svn mv https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.11.0/ https://dist.apache.org/repos/dist/release/incubator/mxnet/ --message "0.11.0 release moving from dev to release repo"   # Wait 24hours for the src mirroring. The final download page for the announce email is somewhere here (example 0.11.0) - https://www.apache.org/dyn/closer.cgi/incubator/mxnet/0.11.0-incubating/

Step 3.1.3: Download the nightly pip build, rename, and publish:(by Sheng)

Step 3.1.4: Build, test, and publish the Docker images: (by Meghna)

• This was done as follows in 0.11.0. In the future use the automated pipeline - 
• Update the tag in the tool.sh file or select the correct tag in the Jenkins Job
• Select the correct Repo name  = mxnet
• Trigger the Job with IS_PUBLISH=false
• Login to the slave and test each image for correct version by checking logs and/or Readme. 
• Manually upload the 20 images that are built. 
• Make sure to update the latest and previous docker images

Step 3.1.5: Verify the resources are uploaded

Check that the resources are present in http://www.apache.org/dist/incubator/mxnet. It may take a while for them to be visible. This will be mirrored throughout the Apache network. There are a few remaining steps.  

Step 3.1.6: Test

Test multinode and multi gpu (kvstore=1)

3.2. Update the MXNet website

...