backport installation guide changes to previous versions by redirecting

[ys2843]

Description

Redirect install page in previous versions to master due to Apache license issues. According to Google Analytics data, 96% of installation guide traffic are from master, the sum of all the other versions (0.11.0 ~ 1.6) only account for 4%. Considering previous version website are all static artifact which are not applicable to make changes. After discussion, we will redirect users to master installation page to avoid showing different versions of docs.

/versions/1.6/get_started
/versions/1.5.1/install/index.html
/versions/1.4.1/install/index.html
/versions/1.3.1/install/index.html
/versions/1.2.1/install/index.html
/versions/1.1.0/install/index.html
/versions/1.0.0/install/index.html
/versions/0.12.1/install/index.html
/versions/0.11.0/get_started/install.html

=> 

/get_started?version=v${version}

Checklist

Essentials

Please feel free to remove inapplicable items for your PR.

• The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
• Changes are complete (i.e. I finished coding on this PR)
• All changes have test coverage:

Changes

• Add rewrite rules to redirect previous versions install page

Comments

• Preview: http://ec2-34-219-134-42.us-west-2.compute.amazonaws.com/

[mxnet-bot]

Hey @ys2843 , Thanks for submitting the PR
All tests are already queued to run once. If tests fail, you can trigger one or more tests again with the following commands:

• To trigger all jobs: @mxnet-bot run ci [all]
• To trigger specific jobs: @mxnet-bot run ci [job1, job2]

---

CI supported jobs: [clang, edge, centos-gpu, miscellaneous, unix-cpu, centos-cpu, sanity, windows-cpu, unix-gpu, windows-gpu, website]

---

Note:
Only following 3 categories can trigger CI :PR Author, MXNet Committer, Jenkins Admin.
All CI tests must pass before the PR can be merged.

[ys2843]

@mxnet-bot run ci [unix-cpu]

[mxnet-bot]

Jenkins CI successfully triggered : [unix-cpu]

[ys2843]

@mxnet-label-bot update [Website]

[mxnet-bot]

Jenkins CI successfully triggered : [unix-cpu]

[mxnet-bot]

Jenkins CI successfully triggered : [website]

[mxnet-bot]

Jenkins CI successfully triggered : [unix-cpu]

[leezu]

Thank you @ys2843. For the forwarding, can you add the respective version number argument in the URL (if possible)? For example, when accessing the install page on 1.2.1, I get forwarded to the get_started page, but the 1.6 version is selected by default. By passing the /get_started?version=v1.2.1 url parameter, the correct version would be specified.

[ys2843]

Thank you @ys2843. For the forwarding, can you add the respective version number argument in the URL (if possible)? For example, when accessing the install page on 1.2.1, I get forwarded to the get_started page, but the 1.6 version is selected by default. By passing the /get_started?version=v1.2.1 url parameter, the correct version would be specified.

Brilliant idea, done.
Just found a version conflict on v1.5, on general version dropdown it is 1.5.0, but in installation guide it is 1.5.1.