wohali commented on issue #149: Create 2.0.x branch? URL: https://github.com/apache/couchdb-documentation/issues/149#issuecomment-317285119 Once we release 2.1 and tag `2.1.0` in the repo, the default https://docs.couchdb.org/ page will redirect to https://docs.couchdb.org/en/2.1.0/. So unless people specifically click on the `2.0.0` link in the documentation footer, they'll always get the updated docs by default. And the 2.0.0 link in the footer will **always** redirect to the `2.0.0` tag, which we shouldn't (and won't) move. We also can't go back and update the docs we shipped in the 2.0.0 tarball, that asset is frozen. We __could__ have a 2.0.x link in the website's footer that would follow the `2.0.x` branch, but I think that would confuse people. The other thing we could do is release a 2.0.1 with various patches and updated docs, at which point we could tag the docs for 2.0.1 and there'd be a link to that on the website. (That'd require a whole lot of cherry-picking, for what it's worth. ? ) @rnewson you were asking about this at one point as well, any opinions? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on 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
