-
Notifications
You must be signed in to change notification settings - Fork 251
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 20.5 #345
Comments
https://github.com/pypa/packaging/blob/master/docs/development/release-process.rst Who wants to cut the release? I'm happy to do so later today, if no one else intends to. :) |
Let's also include #344, and then I'll cut the release. :) |
#344 has been merged, thanks! |
ACK. I'll make a release sometime this week. :) |
@pradyunsg ping? |
@pradyunsg do you plan to release soon? |
I think Pradyun is probably pretty busy with the upcoming pip release, and I doubt additional notifications from this issue is going to help. Might be time to add some release automation via https://github.com/pypa/gh-action-pypi-publish to make this process simpler in the future. |
I'll come around to this this week -- I plan to include this in the upcoming pip release too. :) |
It's up! https://pypi.org/project/packaging/20.5/ Now, to update pip's vendoring and prepare for pip 20.3! :) |
Ohkie -- I did a boo-boo and needed to yank packaging 20.6. packaging 20.7 has been released and you can see the fun stuff in the git graph for the release tags. #359 will help prevent mistakes like this one in the future. :) |
This would include:
LegacyVersion
/LegacySpecifier
(Deprecate LegacyVersion/LegacySpecifier #342)The text was updated successfully, but these errors were encountered: