Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Add the new installation version on the install page: 
    1. Set the new version to be default. See this example: docs/_static/js/options.js.
    2. Add the dropdown option, and all of the new selector classes. See this example: docs/install/index.md.
  • Add news about the new release. See this example: docs/_static/mxnet-theme/index.html.
  • Add download links to the install archives. See this example: docs/install/download.md. Make sure to use the Apache distro servers. 
    1. Current: http://apache.org/dist/incubator/mxnet/
    2. Legacy: http://archive.apache.org/dist/incubator/mxnet/
  • Update the pip package table: http://mxnet.incubator.apache.org/install/ubuntu_setup.html
  • Go to http://jenkins.mxnet-ci.amazon-ml.com/and find job “restricted-website-build”. Login if you're not already.
  • Click Configure and look for the section with the String Parameters.
  • Tags to build
    1. If this is a minor release, the branch should already be in the first parameter "tags_to_build".
    2. If this is a major release, you will need to add the branch to the list in the Default Value field. Note these are semicolon separated values.
  • Tag list
    1. If this is a minor release, you will want to bump the version up for the branch you're updating. Example: change 1.2.0 to 1.2.1.
    2. If this is a major release, you will need to add the new version number to the list. Example: add 1.3.0. Note these are semicolon separated values.
  • Click Save.
  • Click “Build with Parameters”, verify that the settings you just updated look correct, then click Build. 
  • The docs will be published to http://mxnet.incubator.apache.org/. There can be a delay due to some edge caching with Apache infra. The restricted-website-build job also runs four times a day.

...