-
Notifications
You must be signed in to change notification settings - Fork 235
Create 2.0.x branch? #149
Comments
Hi @flimzy, we can certainly create a 2.0.x branch (immediately from the 2.0.0 label) but it's important to note that https://docs.couchdb.org/en/2.0.0/ will always reflect the content of the 2.0.0 tag, as will the contents of our 2.0.0 release tarball which is frozen at this point. The branch will only be used if we decide to release a 2.0.1, which seems unlikely at this point. |
Is there any way to update documentation for corrections, after a release is made? |
Once we release 2.1 and tag We could have a 2.0.x link in the website's footer that would follow the @rnewson you were asking about this at one point as well, any opinions? |
That all makes sense. It's a bit unfortunate; I wish it was possible to improve the documentation on the web site, for previous versions. The 1.6 documentation is in a pretty bad state, and while the 2.0 docs are better, there are still a large number of inaccuracies. In both cases, I think the community could greatly benefit from updated, version-specific docs. |
I agree. The "right" thing to do is to release a 1.6.2 or 2.0.1 with fixes to the docs. I'm open to other ideas. For now I'm going to close this ticket. |
We have a 1.6.x branch for legacy 1.6 documentation, which occasionally gets corrections (at least from me). Now that 2.1.x is nearing release, and 2.0.x is no longer getting new features, we will have a similar situation with the 2.0.x documentation.
My recent PR (#148) appears to touch new features which don't exist in 2.0.x, but it would be nice to update the 2.0.x documentation to reflect the correction made in this PR.
Is creating a 2.0.x documentation branch the best way to do this? And is this a good time to do it?
The text was updated successfully, but these errors were encountered: