Page History

...

1. 1. Bump up the version number. An example can be followed here: https://github.com/apache/incubator-mxnet/pull/6462, update https://github.com/apache/incubator-mxnet/blob/master/setup-utils/install-mxnet-osx-python.sh#L36
      More recent example - https://github.com/apache/incubator-mxnet/pull/8567
      make sure no broken/non-existing links are added to the master branch.
   2. Check with the website lead and docs lead that all necessary updates have made it into the release branch
      1. Most updates happen post-release.
      2. Broken link updates in tutorials and faqs would be an exception.

   3. Create a RSA GPG key of length 4096, upload it to the public server, and add it to the KEYS file (do this process once for each release lead): https://github.com/apache/incubator-mxnet/blob/master/KEYS & https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS See more detailed instructions on creating the key here: https://www.apache.org/dev/openpgp.html#generate-key. Instructions for updating the KEYS file can be found here: https://github.com/apache/incubator-mxnet/blob/master/KEYS#L9-L13. Note that you must use apache email instead of personal email for the key. 
      

      Code Block
      language bash title Adding Keys
      # checkout the apache mxnet repo svn co https://dist.apache.org/repos/dist/dev/incubator/mxnet apache-mxnet cd apache-mxnet # update the KEYS file ... # commit the update svn commit -m “update keys file for xxx ” --username your_username --password your_passwd

      
      

...

Test multinode and multi gpu (kvstore=1)

3.2. Update the MXNet website

...

Now that a new version has been drafted on GitHub with source and pip packages published, we need to update the MXNet website.

• 1. 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 option and all of the new selector classes. See this example: docs/install/index.md.
  2. Add news about the new release. See this example: docs/_static/mxnet-theme/index.html.
  3. Add download links to the install archives. See this example: docs/install/download.md.
  4. Go to http://jenkins.mxnet-ci.amazon-ml.com/and find job “restricted-website-build”. Login if you're not already.
  5. Click Configure and look for the section with the String Parameters.
  6. 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.
  7. 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.
  8. Click Save.
  9. Click “Build with Parameters”, verify that the settings you just updated look correct, then click Build
• Go to http://jenkins.mxnet-ci.amazon-ml.com/job/incubator-mxnet-build-site/
and find job “incubator-mxnet-build-site”. Click “Build with Parameters”, select the release tag, and build
1. . 
2. 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.

Not Sure  Manually update the website’s download links:

...