-
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
7.0.0 release plan #11358
Comments
@AA-Turner is there a way to list which removals that will take place? |
Yep, will be updating CHANGES as usual. If you want the list ahead of time, the majority are enumerated in https://www.sphinx-doc.org/en/master/extdev/deprecated.html (look for a 7.0 removal version). A |
The most notable removal for Sphinx 7 is likely support for HTML 4. |
Thanks @AA-Turner 🙏 |
For testing convenience, could you put up a 7.0b1 release or similar? 🙏 |
I remember that 6.0b1 was out very early, which was highly appreciated. This was very helpful since there was some time to build support for the jQuery removal. From a Read the Docs perspective, it's nice to be able to test out a PyPi release in a few build processes. We do get back some attention from users that either haven't pinned an upper bound on Sphinx or simply want the latest version. If you do a pre-release that works, I will send you back more than crickets ❤️ From a theme/extension perspective, I think it can mean that whoever prioritizes it can bump the Sphinx version dependencies early on. But I guess most maintainers will wait for the stable release before making this effort. |
Sounds good -- I will try and release 7.0rc1 this afternoon (UK time). A |
Sphinx 7.0.0rc1 has been released. A cc: @benjaoming |
Sphinx 7.0.0 has been released. Thanks to all for your contributions. A |
I did just manage to get a 7.0.0rc1 build up on RTD that indicates that we have something working 👍 https://test-builds.readthedocs.io/en/sphinx-7.0.x/ |
I intend to release Sphinx 7 this weekend (though I'm open to arguments to delay).
This release would be only removing expired deprecations, with new features to go in to 7.1.0, to be released around June. I think generally making releases smaller (in terms of delta from the previous release) and slightly more frequent would help debugging -- e.g. in #11354 it was quite hard to pin-point exactly what caused the issue, and crude bisecting of released versions is a useful debug tool.
A
cc: @sphinx-doc/developers
The text was updated successfully, but these errors were encountered: