Skip to content

Release 0.650 planning #5960

Closed
Closed

Description

@JukkaL

I am the release manager for mypy 0.650. I plan to cut the release branch tomorrow (Nov 28) and do the release after a week (Wed Dec 5).

If there are PRs that are low-risk and high-value that ought to go into this release after the branch has been cut please mention them here and I'll see if they can be cherry-picked.

Activity

  1. JukkaL commented on Nov 28, 2018

    @JukkaL
    CollaboratorAuthor

    I'm postponing the branch cut since there are issues with the latest typeshed that are nontrivial to solve (see #5971).

  2. ilevkivskyi commented on Nov 30, 2018

    @ilevkivskyi
    Member

    We probably need to mitigate #5738 (I have a simple workaround - revert some context heuristic).

  3. JukkaL commented on Nov 30, 2018

    @JukkaL
    CollaboratorAuthor

    I've now cut the release branch.

  4. msullivan commented on Nov 30, 2018

    @msullivan
    Collaborator

    I'd like to cherry-pick #5982 to the release branch.

  5. msullivan commented on Nov 30, 2018

    @msullivan
    Collaborator

    Also, as a heads up, when we fix #5983 there is a good chance I'll want to cherry-pick that.

  6. gvanrossum commented on Nov 30, 2018

    @gvanrossum
    Member
  7. emmatyping commented on Dec 1, 2018

    @emmatyping
    Member

    @gvanrossum I have that next on my todo list after figuring out what's wrong in #5983. I will probably get to it on Monday

  8. gvanrossum commented on Dec 1, 2018

    @gvanrossum
    Member

    Assuming the tests pass we should cp #5984, since the script as-is doesn't even work.

  9. emmatyping commented on Dec 3, 2018

    @emmatyping
    Member

    I would like #5994 cherry picked, as it makes the mypy daemon a lot more pleasant to work with on Windows.

  10. JukkaL commented on Dec 3, 2018

    @JukkaL
    CollaboratorAuthor

    Cherry-picked these commits:

  11. JukkaL commented on Dec 3, 2018

    @JukkaL
    CollaboratorAuthor

    We decided to move the release date to Fri Dec 7.

  12. msullivan commented on Dec 4, 2018

    @msullivan
    Collaborator

    I'd like #5997 cherry-picked, so that we will automatically generate mypy_mypyc binaries for the release. This is a purely CI infra change.

  13. JukkaL commented on Dec 4, 2018

    @JukkaL
    CollaboratorAuthor

    Additional cherry-picks:

  14. JukkaL commented on Dec 7, 2018

    @JukkaL
    CollaboratorAuthor

    A dmypy bug is currently blocking the release: #6028

  15. JukkaL commented on Dec 7, 2018

    @JukkaL
    CollaboratorAuthor

    I cherry picked a fix to the dmypy bug: #6029

    I had some issues testing dmypy on Windows, so I won't announce it as officially supported yet. However, I'll mention it as work in progress in case users want to try it out before an official release. I'll do more Windows testing after the release and create issues if needed.

  16. JukkaL commented on Dec 7, 2018

    @JukkaL
    CollaboratorAuthor

    Also dropped the revision history in the documentation (#6018).

  17. ilevkivskyi commented on Jan 2, 2019

    @ilevkivskyi
    Member

    The release is out, so I think we can close this.

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions