Prepare 1.13.0 #480
Merged
Prepare 1.13.0 #480
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Three projects are now using the new theme in production:
Rustworkx is ready to switch after landing a PR to reorganize their docs.
While some projects will still need to reorganize their API docs to be able to switch to the new theme, there are no changes we expect necessary to qiskit-sphinx-theme itself. They can speed up prod builds by reorganizing their API docs, and they can speed up their dev builds even more by using
sphinx-remove-toctrees.If these approaches prove not feasible for the slow docs build, then we can do a qiskit-sphinx-theme 1.14 release with changes to qiskit-sphinx-theme. We are not yet deleting the Pytorch theme. In the meantime, other projects can start switching now.