connorgoggins edited a comment on issue #17798: [Website 2.0] General Version 
Dropdown
URL: 
https://github.com/apache/incubator-mxnet/issues/17798#issuecomment-604149169
 
 
   Another quick update: I have incorporated the feedback from @aaronmarkham 
into the latest version of the preview 
[here](http://ec2-3-19-223-185.us-east-2.compute.amazonaws.com/) (same URL). I 
decided to show the current version in the header for all versions (instead of 
"API Version" for master vs. the current version for the static artifacts). I 
believe this change makes the user interface more consistent across the 
artifacts and the master site, while also making it clear to users which 
version of the site they are currently using. Also happy to revert to a 
"Version (x.y.z)" or "Version (master)" format if that is preferable.
   
   I also found that the tagged release for 1.6.0.rc0 and the branch for v1.6.x 
do not build - there are dependency issues with the build processes for Julia, 
Python, and R docs (see 
[here](http://jenkins.mxnet-ci-dev.amazon-ml.com/blue/organizations/jenkins/docs%2Fconnor-website-build-master/detail/connor-website-build-master/18/pipeline)
 for specific errors). Since each of these docs have different required 
dependencies and each is failing in a unique way, I decided to hold off on 
creating a dynamic pipeline for v1.6 until these issues are resolved. I have 
created a new [Github 
issue](https://github.com/apache/incubator-mxnet/issues/17910) to track 
progress on these build errors.
   
   In the meantime, I have created a 
[document](https://quip-amazon.com/lWalAsADOtrc/MXNet-Website-General-Version-Dropdown-Instructions-for-Adding-Future-Releases)
 to instruct users on how to add future releases to the new version of the 
website, explaining each step of the process from modifying the HTML/CSS of the 
source files to configuring Jenkins pipelines.
   
   If we have consensus that the newly updated preview satisfies the goals of 
this project, I would like to move forward with the final steps of this project 
by submitting a PR with all of my changes and running the Jenkins production 
pipelines to publish the new website. If there is disagreement regarding my 
decision to not build the dynamic pipeline for v1.6, I'm more than happy to 
consider alternate paths forward.

----------------------------------------------------------------
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:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to