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
5. This has a sketch file that can be updated to generate a new png image. Because this file is live and pulled from the web-data repo, you need to submit a PR to this repo with the new image. It is recommended that you add a new one with the version name. Then in your PR for the html updates, you refer to this specific new image, rather than updating the one that is used in production.
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-{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
6. 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'.
7. Prepare and deploy the release version website artifacts, this step requires access permissions to dev Jenkins server
   • Log in to Jenkins pipeline restricted-website-update-versions
   • 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 or 2.0
   • Build and make sure the pipeline finish successfully 

...