-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a stable branch for building docs #812
Comments
In other projects, we've cut branches for each minor release (e.g. v0.2, v0.3, etc.) and then cherrypicked patches in if we needed to do a dot release. Looking at qiskit-terra, that seems to be how they do it as well. |
There will probably be a non-trivial amount of updates needed to the CI (which isn't to say we shouldn't do it, just that it might require some thinking around how to implement it) |
I'd leave it open -- it's something that still needs to be implemented, so this gives us a nice place to track/discuss. |
Not 100% directly related but today I started with #764 so we can think in something similar |
Another option might be to move the docs to their own repo |
I would not disagree with that option. It would be my preferred one. |
Sounds like the solution is to move to a new repo (xref #1166), so we can probably close this one. |
I think so. Closing |
The serverless docs say they reference the latest version released to pip, as they draw the version # from that release; however, the docs are currently built from the
main
branch, which means the docs do not reflect the version they say they do.It would probably be better to have a stable branch from which to build the docs
The text was updated successfully, but these errors were encountered: