Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

Website: Separate master and stable versions of website #17497

Closed
leezu opened this issue Jan 31, 2020 · 2 comments
Closed

Website: Separate master and stable versions of website #17497

leezu opened this issue Jan 31, 2020 · 2 comments
Labels
Feature request Website
Projects
Website Post-Launch

Comments

@leezu
Copy link
Contributor

leezu commented Jan 31, 2020 •
edited

Description

We may want a separate built pipeline and website version for each stable branch + master.

References

For example, https://mxnet.apache.org/get_started/ubuntu_setup will only work for master version of MXNet. This is not a backwards compatibility issue: The previous instructions continue to work for MXNet master. The problem is that users have no way to access the old instructions.
@leezu leezu added this to To do in Website Post-Launch via automation Jan 31, 2020
@leezu leezu moved this from To do to Critical Issue in Website Post-Launch Jan 31, 2020
@eric-haibin-lin
Copy link
Member

We definitely need website versioning for mxnet 2.0

@szha szha mentioned this issue Mar 4, 2020
Closed
@aaronmarkham
Copy link
Contributor

Should probably rename this issue. We don't want to version the website. We want versioned documentation.

@leezu leezu closed this as completed May 28, 2020
Website Post-Launch automation moved this from Critical Issue to Done May 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Feature request Website
Projects
Website Post-Launch
  
Done
Milestone
No milestone
Development

No branches or pull requests
3 participants
@leezu @eric-haibin-lin @aaronmarkham