Skip to content

2.1 release planning #21450

Closed
Closed

Description

@JukkaL

I'm planning to release a small feature release early next week (possibly Mon May 11), based on commit 675b6bf. I'd like to release recent librt/mypyc changes before PyCon US -- that's why the accelerated schedule.

We can still cherry pick low-risk changes to the release branch.

Things we are still missing from the release (feel free to edit):

  • Publish new version of librt
  • Document librt.random

Activity

  1. added
    metaIssues tracking a broad area of work
    on May 9, 2026
  2. JukkaL commented on May 9, 2026

    @JukkaL
    CollaboratorAuthor
  3. ilevkivskyi commented on May 9, 2026

    @ilevkivskyi
    Member

    It would be great to address the performance regression caused by #21262

  4. hauntsaninja commented on May 10, 2026

    @hauntsaninja
    Collaborator

    Would be good to cherry pick:

  5. JukkaL commented on May 10, 2026

    @JukkaL
    CollaboratorAuthor
  6. ilevkivskyi commented on May 10, 2026

    @ilevkivskyi
    Member

    I can make a librt release later today (I am assuming everything we want to sync and release is already in mypy master).

  7. JukkaL commented on May 10, 2026

    @JukkaL
    CollaboratorAuthor

    I can make a librt release later today (I am assuming everything we want to sync and release is already in mypy master).

    Thanks! We have everything on master.

  8. ilevkivskyi commented on May 10, 2026

    @ilevkivskyi
    Member

    @JukkaL librt version bump is now merged and cherry-picked to the release branch.

  9. ilevkivskyi commented on May 10, 2026

    @ilevkivskyi
    Member

    If we don't have a fix for the performance regression caused by #21262 by Monday, we can revert it in 2.1 and release it in 2.2.

    I am fine with this. cc @davidfstr

  10. JukkaL commented on May 11, 2026

    @JukkaL
    CollaboratorAuthor
  11. JukkaL commented on May 11, 2026

    @JukkaL
    CollaboratorAuthor
  12. ilevkivskyi commented on May 21, 2026

    @ilevkivskyi
    Member

    I think we can close this now. It was a relatively small release and no regressions reported so far w.r.t. 2.0.

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

Metadata

Metadata

Assignees

No one assigned

    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