Page History

...

1. Add the new installation version on the get_start page: Set the new version to be default, and add the dropdown option. See this example
2. Add download links to the install archives. See this example. Make sure to use archive.apache.org for all except the current one.
   • Current: http://www.apache.org/dyn/closer.lua?filename=incubator/mxnet/#.#.#/apache-mxnet-src-#.#.#-incubating.tar.gz&action=download
   • Legacy: http://archive.apache.org/dist/incubator/mxnet/
3. Update the pip package table in /python/cpu/pip.md and /python/gpu/pip.md. See this example
4. Update and generate the image file for pip install table.
   • Download pip-packages.sketch from dmlc/web-data repo
   • Use Sketch or other diagram drawing tools to update the sketch file for the new version table (add rows/columns and checkmarks)
   • Save the new pip table as a png file with name pip-packages-{NEW_RELEASE_VERSION}.png
   • Upload the .sketch file and .png file to dmlc/web-data repo. See this example
   • Update pip install table link in pip_snippet.md. See this example
5. Add menu options for general version dropdown. Add the new release version number in _config.ym, _config_beta.tml and _config_prod.yml under '- master'.
6. Update the dropdown versions in header.html. See this example
7. Prepare and deploy the release version website artifacts, this step requires access permissions to CI Jenkins server
   • Log in to Jenkins pipeline restricted-website-update-versions
   • Goto Configure to make sure the Git Repository URL points to https://github.com/apache/incubator-mxnet.git
   • Click Build with Parameters on the left panel
   • Specify COMMIT_ID to the release branch
   • Specify FOLDER_NAME to the release version, e.g. 1.8.0 or 2.0.0
   • Build and make sure the pipeline finish successfully 

...

1. Cherry-pick above changes (step 1-5 in 3.2.1) from release branch to master branch. See this example
2. Set default website version to new release version by updating the RewriteRule in /docs/static_site/src/.htaccess under comment "# Set default website version to current stable". For example: update the version 1.x to the new release version: 
   • RewriteRule ^(.*)$ /versions/1.x/$1 [r=307,L] => RewriteRule ^(.*)$ /versions/{NEW_RELEASE_VERSION}/$1 [r=307,L]
3. Publish website artifact to the main website
   • Manually trigger pipeline restricted-website-build-master to publish the new website artifact. Make sure that the pipeline finishes successfully.
   • The new website will be published to http://mxnet.incubator.apache.org/. There can be a delay due to some edge caching with Apache infra.
   • After publishing, check the correctness of the main website

...