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 0.640 planning #5741

Closed
gvanrossum opened this issue Oct 5, 2018 · 4 comments
Closed

Release 0.640 planning #5741

gvanrossum opened this issue Oct 5, 2018 · 4 comments

Comments

@gvanrossum
Copy link
Member

I am the release manager for mypy 0.640. I plan to cut the release branch right now (Oct 5) and do the release in a week (Oct 12).

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

@ilevkivskyi
Copy link
Member

I think we should decide what to do about #5738, because technically it is a regression. Possible options are:

  • Don't care about this for now, it is minor and is caused by an old bug exposed by a fix to another issue.
  • Implement a simple fix (unfortunately I don't have one yet, sorry, but it should not be hard) just to avoid the false positive.
  • Revert the switch from all to invariant instance contexts.

gvanrossum added a commit that referenced this issue Oct 5, 2018
Last one planned for release 0.640 (see #5741)
@gvanrossum
Copy link
Member Author

Release branch created: https://github.com/python/mypy/tree/release-0.640

It's currently identical to master -- the last commit is "Fix infinite loop on corrupted fine-grained cache (#5739)".

Anything that we decide should go into this release will be cherry-picked.

This was referenced Oct 7, 2018
gvanrossum added a commit that referenced this issue Oct 9, 2018
Follow-up for #5691. Should be cherry-picked into the release (#5741). Fixes #5757.
gvanrossum added a commit that referenced this issue Oct 9, 2018
Follow-up for #5691. Should be cherry-picked into the release (#5741). Fixes #5757.
@gvanrossum
Copy link
Member Author

I went through all of the motions of the release, but within minutes a regression was found (#5784) so I had to withdraw the release. There will be a new one Monday.

@msullivan
Copy link
Collaborator

0.641 got released a while ago

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants