-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Pip next release ETA #4372
Comments
So, I found another similar question (about release schedule) that was answered, and noticed the 10.0 milestone. That gives me a partial answer. I'll keep this open for now for the "what can be done to help, because I'm eager for the next release" part mentioned above. Thanks! |
Hopefully, pip 10.0 should be released within in a few weeks. Your PR in packaging should now be unlocked which would allow a new release of Help is always welcome, mainly in issues triaging as it is time-consuming but also PR reviews or bug fixing :) |
Going to close this since @xavfernandez it seems answered most of the questions :) |
We're several months down the road now, is there any update on this? Personally, I'm waiting for #4393 |
@SpoonMeiser (I think you know; anyway saying) There's a 10.0 milestone in the tracker. There's currently 4 issues and 2 PRs in that milestone. Once the milestone is completed, pip 10.0 would be released and the milestone closed. |
I'd like to ask if there's an ETA for the next Pip release.
(And also, ask if there's anything I can do to help out for the release.)
I was initially going to ask about Pip 9.0.2 bugfix release, but a little search accross the merged PRs pointed me that the next one will probably be 10.0.0.
There are some bugfixes that would be nice to see released (in my case, PR #4294, as it blocks my own PR in packaging, to unblock #4356).
Of course, since it appears we are set for a major release, that's probably more work than a simple bugfix.
And of course, I don't want to rush anything or anyone, I'm only asking, and offering my help, since I'm the one to ask.
Thanks!
(P.s. If this is not the right place to discuss this, feel free to point me to the right place and close this.)
The text was updated successfully, but these errors were encountered: