4.0.0 release plan

[tk0miya]

According to our annual release cycle, this April is time for the major release.
I think this schedule is good for the release. What do you think?

• Apr 10th:
  • Beta release (feature freeze)
  • call for translation
  • Create a new branch: 4.x and 4.0.x
    • 4.x will be used for develop 4.1
    • 4.0.x will be used for develop 4.0.0 (feature freezed)
• Apr 24th: final release

Any comments?

Note: issues marked as 4.0.0: https://github.com/sphinx-doc/sphinx/milestone/74

[shimizukawa]

㊗️

[ericholscher]

Is it possible to have the release done on a weekday, so that if major issues are hit with RTD or other downstream users, we can be around to fix them? I realize it's a trade off between folks who are doing this work in their jobs vs. free time -- but I do think it might be best to ship them on a weekday, if possible.

We just hit this with the docutils release, and woke up Monday morning to a number of bug reports, so it would be great to coordinate this stuff a bit more. Certainly some of this can be caught in testing, but there's such a widespread user base, there will always be edge cases we can't catch in beta.

[grubert]

On Tue, 6 Apr 2021 at 18:42, Eric Holscher ***@***.***> wrote: Is it possible to have the release done on a weekday, so that if major issues are hit with RTD or other downstream users, we can be around to fix them?

I realize it's a trade off between folks who are doing this work in their

jobs vs. free time -- but I do think it might be best to ship them on a weekday, if possible.

that is my tradeoff sorry for hitting anyone with docutils 0.17 We just hit this with the docutils release, and woke up Monday morning to a

number of bug reports, so it would be great to coordinate this stuff a bit more. Certainly some of this can be caught in testing, but there's such a widespread user base, there will always be edge cases we can't catch in beta.

do you have a test loading prerelease stuff once a ... week so that if a beta is out for two weeks is this safer or is it simply release on ... tuesday (not the first day into week but not already weakened by days)

…

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#9056 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHEYA4SN4TYSDI6YYIYTYLTHM2YRANCNFSM42LDEIZQ> .

[tk0miya]

I don't know I will have time on weekdays. But it's not impossible.

[jakobandersen]

I'm hoping to get #9023 and #8313 done for v4 due to (semi-)breaking changes. However, the latter requires #8929 to avoid breaking existing intersphinx functionality for the C domain. @tk0miya, are you fine with the design of it?

[tk0miya]

Now, I don't have time to review #8929 in detail. But I think env and domains should not be coupled with intersphinx. So I'd like to implement it on 4.1.