-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Release 0.610 planning #5096
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
Comments
So we definitely need to do something about google/protobuf in typeshed (python/typeshed#2154), i.e. PR python/typeshed#2157 (now merged into master). |
Actually we're gonna cut the release branch on Tuesday, because Monday is a holiday in the United States |
Going to cut the release branch today, but postponing the release until Monday |
#5122 should be a release blocker. |
Hm, I think I can fix it. I reviewed the PR that likely causes this. |
Thanks for fixing that one! I just checked our codebase against master again and got a few other errors: #5124 (almost certainly related to the overload refactor that won't go into 0.610) and a false positive about an incompatible return type on an async method with a decorator, which I haven't had time to minimize yet. |
Overload PR is not in the release branch, see above. I am much more interested in
Because this one is in the release branch. |
[Edit: this might not be a bug and doesn't need to block the release.] |
#5123 cherry-picked |
|
OK since the pace of things that we need to cherry-pick has been continuing unabated all week, I am postponing the release another week so that we can validate it more. |
I believe that f3cb59a is now a release candidate. |
Cherry picking the documentation patch #5157 |
Cherry picked the documentation patch #5164 |
Release out! |
Just wanted to say what a massive difference 0.610 has made to my daily workflow. Having flycheck on emacs run |
I'd like to release mypy 0.610 on Friday June 8. Aiming to cut the release branch on Tuesday May 29.
If there are any PRs that urgently need merged, mention them here.
The text was updated successfully, but these errors were encountered: