Skip to content

Release 1.2 planning #14916

Closed
Closed

Description

@JukkaL

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

Activity

  1. added
    metaIssues tracking a broad area of work
    on Mar 17, 2023
  2. JukkaL commented on Mar 23, 2023

    @JukkaL
    CollaboratorAuthor

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

  3. JukkaL commented on Mar 23, 2023

    @JukkaL
    CollaboratorAuthor

    This hopefully fixes release blocking build issues in some configurations:

  4. JukkaL commented on Mar 23, 2023

    @JukkaL
    CollaboratorAuthor

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

  5. self-assigned this
    on Mar 23, 2023
  6. JukkaL commented on Mar 23, 2023

    @JukkaL
    CollaboratorAuthor

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

  7. wesleywright commented on Mar 25, 2023

    @wesleywright
    Collaborator

    Another tiny dataclass_transform fix: #14958

  8. tyralla commented on Apr 1, 2023

    @tyralla
    Collaborator

    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.

  9. AlexWaygood commented on Apr 4, 2023

    @AlexWaygood
    Member
  10. JukkaL commented on Apr 5, 2023

    @JukkaL
    CollaboratorAuthor

    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.

  11. JukkaL commented on Apr 5, 2023

    @JukkaL
    CollaboratorAuthor
  12. JukkaL commented on Apr 5, 2023

    @JukkaL
    CollaboratorAuthor

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

  13. JukkaL commented on Apr 6, 2023

    @JukkaL
    CollaboratorAuthor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

metaIssues tracking a broad area of work

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions