Skip to content

Release 0.930 planning #11700

Closed
Closed

Description

@JukkaL

I'm planning another release fairly soon after 0.920 (#11158) is out to catch up with the GitHub master branch. If everything goes as planned, I'll cut the release branch around Tue 14 Dec. Please post here any PRs that you'd like to include in the release and that are not yet in master (or in the release branch after I've created it).

Note: Please do not sync typeshed until I've created the release branch. There are already some typeshed regressions that likely need to be resolved. If you want to include some specific typeshed changes, I can potentially cherry-pick them.

Activity

  1. JukkaL commented on Dec 10, 2021

    @JukkaL
    CollaboratorAuthor

    Regression that is a release blocker: #11699 (_order_ in enum)

  2. self-assigned this
    on Dec 10, 2021
  3. JukkaL commented on Dec 10, 2021

    @JukkaL
    CollaboratorAuthor

    Another regression: #11701 (Literal[True, False] false positives)

  4. JukkaL commented on Dec 10, 2021

    @JukkaL
    CollaboratorAuthor

    Another regression that might be a release blocker (but it might be very rare and not super important to fix): #11702 (enum inheritance false positive)

  5. JukkaL commented on Dec 10, 2021

    @JukkaL
    CollaboratorAuthor

    Yet another regression that looks like a release blocker: #11704 (need type annotation with contextmanager)

  6. JukkaL commented on Dec 10, 2021

    @JukkaL
    CollaboratorAuthor

    One more regression: #11705 ("and" type inference with strict optional disabled)

  7. hauntsaninja commented on Dec 11, 2021

    @hauntsaninja
    Collaborator

    Currently unmerged PRs I'd like included:
    #11681 (low risk, fixes a crash)
    #11708 (low risk, removes an optimisation that resulted in a regression reported multiple times)
    #11709 (fixes #11701 as mentioned above)
    If possible, enough of #10191 that we no longer crash on match statements

    Curious if @sobolevn has thoughts on any PRs to prioritise

  8. Zac-HD commented on Dec 12, 2021

    @Zac-HD
    Contributor

    #11718 keeps biting me, and should be pretty easy to merge.

  9. JukkaL commented on Dec 14, 2021

    @JukkaL
    CollaboratorAuthor

    Two planned reverts to avoid regressions: #11741 (Python 2 division), #11743 (Python 2 raise), unless there's a forward fix very soon.

    Some cherry-picks from typeshed to avoid regressions: #11739

  10. sobolevn commented on Dec 14, 2021

    @sobolevn
    Member

    unless there's a forward fix very soon.

    Sorry, I won't be able to submit a fix before the weekend. If this is fine 🙂
    Or you can always keep this out of scope of the release, these two feature are not very important.

  11. JukkaL commented on Dec 14, 2021

    @JukkaL
    CollaboratorAuthor

    Sorry, I won't be able to submit a fix before the weekend

    No worries, I reverted the PRs now so that they won't block the release.

  12. cdce8p commented on Dec 15, 2021

    @cdce8p
    Collaborator

    Don't know if there is still some time left but I believe #10712 would be a good feature to have.

  13. hauntsaninja commented on Dec 16, 2021

    @hauntsaninja
    Collaborator

    I'd like this typeshed PR to be included: python/typeshed#6591 (fixes a regression shipped with 0.920)

  14. 18 remaining items

  15. JukkaL commented on Jan 4, 2022

    @JukkaL
    CollaboratorAuthor

    I'm planning to publish a 0.931 bugfix release later this week (current estimate is Wed or Thu). Thank you everybody who contributed fixes to regressions, and thank you @hauntsaninja for the useful summary!

    In addition to the PRs mentioned above, this also fixes a regression:

  16. A5rocks commented on Jan 6, 2022

    @A5rocks
    Collaborator

    #11913 is also a regression it seems.

  17. hauntsaninja commented on Jan 6, 2022

    @hauntsaninja
    Collaborator

    #11912 fixes a minor regression in 0.930 (caused by a changed in typeshed stubs)

    #11918 and #11863 are not a regression, but would make typeshed folks happy. We indicated we'd be willing to issue point releases for this in python/typeshed#4820 (comment)

  18. JukkaL commented on Jan 6, 2022

    @JukkaL
    CollaboratorAuthor

    I cherry-picked these additional fixes:

    Since there are still a few regressions without a fix, I will wait until tomorrow (Friday) before making the release. If important regressions are still open tomorrow, I can make a 0.932 release once we have the remaining fixes.

  19. JukkaL commented on Jan 6, 2022

    @JukkaL
    CollaboratorAuthor

    Another potential regression:

  20. hauntsaninja commented on Jan 7, 2022

    @hauntsaninja
    Collaborator

    #11717 was merged, but not backported
    I believe right now #11924 is the only open PR that fixes a regression

  21. sobolevn commented on Jan 7, 2022

    @sobolevn
    Member

    PR with stubtest bugfix: #11931
    This would be helpful for typeshed

  22. JukkaL commented on Jan 7, 2022

    @JukkaL
    CollaboratorAuthor

    I'm planning to include this PR in the release:

  23. JukkaL commented on Jan 7, 2022

    @JukkaL
    CollaboratorAuthor

    Two final cherry-picks for 0.931:

    We should be ready for the release soon, once the wheel build completes. I'll need to prepare a short release blog post as well.

  24. JukkaL commented on Jan 7, 2022

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

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions