Jukka Lehtosalo
Jukka Lehtosalo
> Though I'm not sure that's really necessary. Yeah it doesn't seem necessary, but if it doesn't take any significant effort, I think it's still worth doing. 3.8 still appears...
Let's make the decision when we are closer to 1.13 release? If there have been significant regressions or issues with new functionality in 1.12 (that we haven't fixed in a...
We are aiming at having another release branch created in late October/early November. If we can stick to this schedule, I think we can manage another feature release with 3.8...
We can merge this after the release branch for 1.14 has been created.
Updated the release branch to use a more recent commit as a base (9e45dadcf6d8dbab36f83d9df94a706c0b4f9207 from May 13). The current ETA for the release is around Tue May 27. PyCon US...
Changelog PR: * https://github.com/python/mypy/pull/19138 I'm planning to merge these documentation updates to the release branch: * #19153 * #19154
The release was delayed to Wednesday because of a few missing bits of documentation (see above).
Likely Europe afternoon / US morning
Some regressions have been reported, even before the release is out (which is better than after the release!). It's possible some of them are release blockers: * #19139 * #19146...
For #19139 we have the option of reverting the PR and re-applying it afterwards once there's a fix to the issue. However there were merge conflicts so it's not entirely...