Skip to content
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.3.0 release plan #12242

Closed
AA-Turner opened this issue Apr 9, 2024 · 16 comments
Closed

7.3.0 release plan #12242

AA-Turner opened this issue Apr 9, 2024 · 16 comments
Assignees
Milestone

Comments

@AA-Turner
Copy link
Member

I intend to release Sphinx 7.3.0 reasonably soon (perhaps around the 14-16th; though I'm open to arguments to delay).

Given the volume of commits since 7.2.0, it's possible that we have accidentally made breaking changes. Being said, I think I'd still prefer to do 7.3.0 now and then 8.0 as a 'clean' release just removing depreciations.

Please let me know if there are any features or bugfixes you would like to have included in the release, or any other matters.

A

cc: @sphinx-doc/developers @sphinx-doc/triagers

@AA-Turner AA-Turner added this to the 7.3.0 milestone Apr 9, 2024
@AA-Turner AA-Turner self-assigned this Apr 9, 2024
@AA-Turner
Copy link
Member Author

AA-Turner commented Apr 9, 2024

Open issues:

@jayaddison

This comment was marked as resolved.

@chrisjsewell

This comment was marked as resolved.

@jfbu

This comment was marked as resolved.

@AA-Turner AA-Turner pinned this issue Apr 9, 2024
@jayaddison

This comment was marked as resolved.

@picnixz

This comment was marked as resolved.

@picnixz

This comment was marked as resolved.

@danieleades

This comment was marked as resolved.

@adamtheturtle

This comment was marked as resolved.

@wlach

This comment was marked as resolved.

@AA-Turner
Copy link
Member Author

Sphinx 7.3.0 has been released.

A

@picnixz
Copy link
Member

picnixz commented Apr 19, 2024

@AA-Turner Do you think it's worth to set-up some bot job just before releasing to check whether we break any themes due to our changes? like mypy_primer? We could either run the job manually or we could run the job before releasing (and also, theme maintainers could give us some test examples to check)

@hugovk
Copy link
Contributor

hugovk commented Apr 19, 2024

And perhaps the docs build could dogfood the current Sphinx:

https://github.com/sphinx-doc/sphinx/blob/master/.github/workflows/builddoc.yml

For all supported Python versions:

  1. Install Sphinx from master
  2. Build the Sphinx docs

Or expand step 1 to also test packaging:

  1. Build wheels, install from wheel
  2. Build the Sphinx docs

@trallard
Copy link

trallard commented Apr 30, 2024

Quick chime in.
We are in the process of improving our tests and CI for PyData Sphinx Theme. Which should help us identify breaking changes/incompatibilities with Sphinx main sooner and more reliably.

I'll do my best to flag any issues we see on our end, especially as y'all plan upcoming releases if you think that would be useful on your end to reduce churn.

Some of the changes we are adding to our CI follow the pattern mentioned above by @hugovk (build and test with the build) so happy to lend a hand if needed on your end too shall you decide to test on your end for theme's breaking.

@AA-Turner AA-Turner unpinned this issue May 2, 2024
@picnixz
Copy link
Member

picnixz commented May 4, 2024

Thank you @trallard and @hugovk for your suggestions. When I'm done with the thesis' manuscript, I'll come back to ask for some ideas and suggest a proposal. I'll open a separate issue at that time and will tag you along (or maybe a discussion, I'll see when the time comes).

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

10 participants