leezu commented on issue #17798: [Website 2.0] Versioned Dropdown for Python API Docs URL: https://github.com/apache/incubator-mxnet/issues/17798#issuecomment-597400329 Thanks @connorgoggins for clarifying. My point is, the website on the 1.6 branch should currently not be broken (or easy to fix) and we can avoid it from breaking in the future. The website on the master branch is not broken either. The Jenkins job publishing the website currently can be run for the 1.6 branch, 1.7 branch and master branch and we can enable it for more branches when new releases are made. The Jenkins jobs can be modified to build `https://mxnet.apache.org/v1.6/` for 1.6, `https://mxnet.apache.org/v1.7`, `https://mxnet.apache.org/master/` respectively. We can include older releases statically as per @aaronmarkham's suggestion. In such case all that is needed would be a static banner or dropdown that contains links to the newer versions of the website. As an example, consider the banner at the top of https://cmake.org/cmake/help/v3.11/module/FetchContent.html . This would solve the versioning issue for all parts of the website and should not exceed 4 weeks work. It may be even simpler than extending the Python docs as per your proposal. What do you think?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
