freeze DVC 1.0 docs version

[shcheklein]

As we are getting ready for 2.0 release, as @skshetry reminded us, it's better to freeze docs:

• create a branch and a tag for the current state (before we merge any DVC 2.0 changes)

• create a subdomain for 1.0 docs - v1.dvc.org ?

• add selector, mention in the docs that this is the latest version and previous exists (similar to Elastic docs?)

• Consider also docs: publish as ebook/plain html/pdf or other formats gatsby-theme-iterative#35 (or close it)

[jorgeorpinel]

create a branch and a tag for the current state (before we merge any DVC 2.0 changes

We can manage a v1 branch to keep merging some changes there because I'm pretty sure we will continue to make updates that also apply to 1.x for some time. Not sure we need a tag.

create a subdomain... v1.dvc.org

👍

[jorgeorpinel]

Update on this: So far everything on master is also part of v1 so I've been merging it back. At some point soon they will start to diverge. 2 comments: 1) how about adopting https://mergify.io/features/backports to send back certain changes to v1 after that? 2) Should this issue be prioritized/assigned? Thanks

[jorgeorpinel]

Another Q. Can we remove the blog and probably other sections (which may become outdated) from the v1 website?

And should we prioritize or merge iterative/gatsby-theme-iterative#35 with this one?

[shcheklein]

Closing this, not important anymore. Also I think we should with a Python style docs (add notes per features) rather than trying to support multiple versions.