Page History

...

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

Step 2:

...

Rename and publish the source package:

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. 

Step 3: 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

First upload to dev and then move to releases as follows 

#create a directory under releases -  https://httpd.apache.org/dev/release.html

tar -zxvf apache-mxnet-src-0.11.0.rc3-incubating.tar.gz
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
 
svn mv https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.11.0/ http://www.apache.org/dist/incubator/mxnet/mxnet-#.#.#

...

-#.#.#

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

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

• • TODO

Step 5: Verify the resources are uploaded

...