-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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.650 planning #5960
Comments
I'm postponing the branch cut since there are issues with the latest typeshed that are nontrivial to solve (see #5971). |
We probably need to mitigate #5738 (I have a simple workaround - revert some context heuristic). |
I've now cut the release branch. |
I'd like to cherry-pick #5982 to the release branch. |
Also, as a heads up, when we fix #5983 there is a good chance I'll want to cherry-pick that. |
@gvanrossum I have that next on my todo list after figuring out what's wrong in #5983. I will probably get to it on Monday |
Assuming the tests pass we should cp #5984, since the script as-is doesn't even work. |
I would like #5994 cherry picked, as it makes the mypy daemon a lot more pleasant to work with on Windows. |
Cherry-picked these commits:
|
We decided to move the release date to Fri Dec 7. |
I'd like #5997 cherry-picked, so that we will automatically generate |
Additional cherry-picks:
|
A dmypy bug is currently blocking the release: #6028 |
I cherry picked a fix to the dmypy bug: #6029 I had some issues testing dmypy on Windows, so I won't announce it as officially supported yet. However, I'll mention it as work in progress in case users want to try it out before an official release. I'll do more Windows testing after the release and create issues if needed. |
Also dropped the revision history in the documentation (#6018). |
The release is out, so I think we can close this. |
I am the release manager for mypy 0.650. I plan to cut the release branch tomorrow (Nov 28) and do the release after a week (Wed Dec 5).
If there are PRs that are low-risk and high-value that ought to go into this release after the branch has been cut please mention them here and I'll see if they can be cherry-picked.
The text was updated successfully, but these errors were encountered: