-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
6.0.0 release plan #10920
Comments
Sphinx 6.0.0b1 has been released. From now, no breaking changes should be merged. A |
@AA-Turner Is there a way you could ping from such release announcement? For some reason I do not configure my github account to receive email notifications on all issue creations. So I missed this. Else I would have pushed some PR to make Sphinx by default use for pdf via latex modified rendering of code-blocks and tables (refer in particular #10620). Now, this would be considered breaking in LaTeX world but may not be so in Sphinx. It is my estimate that only a minority of Sphinx users actually care about the pdf looks. But if such change (for example code-blocks always with some light background and rounded corners) is breaking I can now not merge it until probably 7.0.0... |
@jfbu sorry; I will ping in future. If you can push your PR before Monday I will release beta 2 with the change, I think it will still be fine as we have 2 months until final release. A |
@AA-Turner ah ok good. Even if you had pinged me I would have missed the beta 1 as I had some other tasks this week-end such as biking... |
Do let me know if you make the PR (ping/etc), I think a cosmetic change (rendering) is not breaking for Sphinx on further thought, as it does not affect our APIs or other contracts. That means it could go in 6.0b2, 6.0, 6.1, etc. A |
@AA-Turner I have done a PR #10924, but now I am not sure about how to modify CHANGES, in view of
it looks as if "Incompatible changes" section is not appropriate. I have added to CHANGES an entry in "Features added" with a pointer on how to revert the rendering change if so desired. I will merge #10924 so that it can be beta-tested and if it causes trouble we can revert. |
Thanks @hugovk for tip, but my issue here was to get notified before actual release from the dedicated issue created to gather maintainers dialog about it ;-) |
Sphinx 6.0.0b2 has been released. |
I intend to release Sphinx 6 later today. A |
Sphinx 6.0.0 has been released. A |
I intend to release the first beta of Sphinx 6.0.0 today. This will allow extensions to beta-test against the new version of Sphinx. 6.0.0 final will be released no earlier than 01/12/22.
Issues marked against 6.0.0: sphinx-doc/sphinx/milestone/125
A
The text was updated successfully, but these errors were encountered: