-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Release 0.640 planning #5741
Comments
I think we should decide what to do about #5738, because technically it is a regression. Possible options are:
|
Last one planned for release 0.640 (see #5741)
Release branch created: https://github.com/python/mypy/tree/release-0.640 It's currently identical to master -- the last commit is "Fix infinite loop on corrupted fine-grained cache (#5739)". Anything that we decide should go into this release will be cherry-picked. |
I went through all of the motions of the release, but within minutes a regression was found (#5784) so I had to withdraw the release. There will be a new one Monday. |
0.641 got released a while ago |
I am the release manager for mypy 0.640. I plan to cut the release branch right now (Oct 5) and do the release in a week (Oct 12).
If there are PRs that are low-risk and high-value that ought to go into this release please mention them here and I'll see if they can be cherry-picked.
The text was updated successfully, but these errors were encountered: