Release 0.610 planning

[msullivan]

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.

[gvanrossum]

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).

[msullivan]

Actually we're gonna cut the release branch on Tuesday, because Monday is a holiday in the United States

[msullivan]

Going to cut the release branch today, but postponing the release until Monday

[msullivan]

Release branch is cut, with a cherry pick to include #5120 but exclude #5084.

I have a documentation patch about dmypy run that I intend to write and cherry-pick. I don't think we have any other planned cherry picks?

[ilevkivskyi]

Release branch is cut, with a cherry pick to include #5120 but exclude #5084.

👍 Perfect!

[JelleZijlstra]

#5122 should be a release blocker.

[ilevkivskyi]

Hm, I think I can fix it. I reviewed the PR that likely causes this.

[JelleZijlstra]

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.

[ilevkivskyi]

Overload PR is not in the release branch, see above. I am much more interested in

a false positive about an incompatible return type on an async method with a decorator

Because this one is in the release branch.

[JelleZijlstra]

#5125.

[Edit: this might not be a bug and doesn't need to block the release.]

[msullivan]

#5123 cherry-picked

[msullivan]

Oh and #5053 should be probably done

[msullivan]

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 plan to cherry-pick #5132 and #5126, and then we will hopefully have an actual "release candidate".
(Though there will still be a documentation patch I need to write and cherry-pick.)

[msullivan]

I believe that f3cb59a is now a release candidate.