Skip to content
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 1.2 planning #14916

Closed
2 tasks done
JukkaL opened this issue Mar 17, 2023 · 11 comments
Closed
2 tasks done

Release 1.2 planning #14916

JukkaL opened this issue Mar 17, 2023 · 11 comments
Assignees
Labels
meta Issues tracking a broad area of work

Comments

@JukkaL
Copy link
Collaborator

JukkaL commented Mar 17, 2023

I'm planning to make a 1.2 release either around Mar 23 or April 4 (tentative timeline; I'm on vacation between the dates).

Please post here any issues you'd like to see fixed in the release, or PRs you'd like to have merged. I'll cut the release branch around Mar 21.

Here are a few things I'd like to have in the release:

  • Remaining dataclass transform fixes (if not included in a 1.1.x bug fix release)
  • Document native integers and native floats in mypyc
@JukkaL JukkaL added the meta Issues tracking a broad area of work label Mar 17, 2023
@JukkaL
Copy link
Collaborator Author

JukkaL commented Mar 23, 2023

A minor regression introduced with recent typeshed changes that trigger a bug:

@JukkaL
Copy link
Collaborator Author

JukkaL commented Mar 23, 2023

This hopefully fixes release blocking build issues in some configurations:

@JukkaL
Copy link
Collaborator Author

JukkaL commented Mar 23, 2023

Fix to another release blocker (already merged) that fixed wheel builds:

@JukkaL JukkaL self-assigned this Mar 23, 2023
@JukkaL
Copy link
Collaborator Author

JukkaL commented Mar 23, 2023

I've now cut the release branch: https://github.com/python/mypy/tree/release-1.2

Fixes to bugs, documentation updates, and dataclass transform improvements can still be cherry-picked to the release branch.

I expect the release to go out around April 4. I will be on vacation the next week, but I will follow this issue (but not every day).

@wesleywright
Copy link
Collaborator

wesleywright commented Mar 25, 2023

Another tiny dataclass_transform fix: #14958

@tyralla
Copy link
Collaborator

tyralla commented Apr 1, 2023

Could you cherry-pick 1dd26a3? When using 1.1.1, I need to add unspecific "type ignore" (misc) commands to many class definitions in my code base that could hide actual bugs. With 1dd26a3, the problem should be gone.

@AlexWaygood
Copy link
Member

A minor regression introduced with recent typeshed changes that trigger a bug:

This PR claims to have a fix:

@JukkaL
Copy link
Collaborator Author

JukkaL commented Apr 5, 2023

I cherry-picked these PRs:

#14975 needs some more work, but we can cherry-pick it if it is completed soon (or we can include it in a point release).

I'd still like to include #14870. I'm working on finishing it.

@JukkaL
Copy link
Collaborator Author

JukkaL commented Apr 5, 2023

Also cherry-picked this final dataclass transform fix:

@JukkaL
Copy link
Collaborator Author

JukkaL commented Apr 5, 2023

Now that we have all essential fixes in, I'm planning to make the release tomorrow (Thu Apr 6).

@JukkaL
Copy link
Collaborator Author

JukkaL commented Apr 6, 2023

The release is now out: https://mypy-lang.blogspot.com/2023/04/mypy-12-released.html

@JukkaL JukkaL closed this as completed Apr 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Issues tracking a broad area of work
Projects
None yet
Development

No branches or pull requests

4 participants