aaronmarkham commented on issue #17798: [Website 2.0] Versioned Dropdown for 
Python API Docs
URL: 
https://github.com/apache/incubator-mxnet/issues/17798#issuecomment-597399954
 
 
   My suggestion is to just grab the old artifacts from the previous site 
builds here:
   http://jenkins.mxnet-ci.amazon-ml.com/job/restricted-website-build/
   This unzips to yield a versions folder that has artifacts for the following 
versions:
   
![2020-03-10_18-26-44](https://user-images.githubusercontent.com/5974205/76373095-b4092400-62fc-11ea-82d9-1557e4796456.png)
   It's pretty much just C and Python and a little bit of Scala up to 1.2.1, 
then Scala's docs really come out, and then over time we get Clojure, Java and 
Julia. Perl is offsite. R wasn't generated in a pipeline until this new site. I 
could try to generate pdfs for old R versions if there was demand.
   Anyways, for the C, Scala, Clojure, Java, and Julia microsites, we just grab 
those and deploy them as static assets. 
   If you want to fix C and split out C and C++ APIs, then we'll need to create 
some custom Doxyfiles for that and split the pipeline into two... maybe add a 
new tile for that. I'd leave that for later though.
   For the Python versions, I'd focus on current stable, 1.7+ and master (2.x). 
If we want the old ones then just keep the old look and feel for when those get 
launched. Otherwise, there's a bunch of tech debt where you'd have to patch the 
old branches to make the docs build properly. Limited bang for the buck IMO.
   

----------------------------------------------------------------
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

Reply via email to