Looking at https://docs.readthedocs.io/en/stable/versions.html, they
recognize an explicit "stable" tag or just picks the latest semantic
version branch or tag. They use https://peps.python.org/pep-0440/
rules to parse and that allows for a ".postN" suffix for a tag/branch.
So we could have a 3.2.2
+1, for the branch renaming part
For the docs integration part, I’m at ± 0:
Is it possible to distinguish what has been changed in a repository? For
example:
Are there changes in
- /docs -> rebuild and publish docs
- /src -> couchdb ci run
Or is it an all or nothing approach of PR’s in GitHub
I'm fully in favor of part 1, +1
On the docs, I'd say a slightly hesitant +1 as is, given the situation
Jan describes. I still think it would be an improvement to merge the
repo since PRs which correctly update couchdb+docs would more likely
keep changes and their docs together. Aside from direct
Heya Nick,
thanks for taking my raw idea to the larger group here :)
The one other point that started the whole thing is our publishing of docs.
We have a stable and a latest tag where latest just tracks the main branch
on the docs repo and stable we move manually when a new release comes out.
