Release 19.3!

[chrahunt]

A new release!

This would enable use of #6770 and other new improvements.

Additional context

• Release 19.2 #6630
• Release Cadence

[pradyunsg]

Our release month would be October. But I'm always up for figuring out our release manager early. 🙃

@xavfernandez had expressed interest in being the RM this month. As usual, I'm up for doing this if no one else is willing to pick this up. :)

[atugushev]

@pradyunsg please ping me when you start preparing a release. I'll do quickly a pip-tools release. Thanks :)

[pradyunsg]

Knock knock @pypa/pip-committers -- who wants to be the RM? I'm gonna assume it's me if no one responds expressing interest by next week, Friday. :)

[xavfernandez]

@pradyunsg I'm still interested :) . If there is nothing important to wait (like #7102) I'll aim for a release during week 41.

[pradyunsg]

Looking at the rollout planned above, I think so?

I mean, we'd want to support exactly (or a subset of tags of) what PyPI accepts. As long as the PR does that and there's no mismatch, I'm cool to merge it, since AFAICT, the changes are decent there.

@xavfernandez could you please flag on the manylinux2014 rollout issue that the changes needed are not reflected in the TODO list for rollout?

[pradyunsg]

Alrightly, we have our release manager for pip 19.3: @xavfernandez. :)
_{(unless other @pypa/pip-committers holler)}

[pradyunsg]

There's a thing to be removed for pip 19.3 -- pip config --venv. Filing a PR for that.

[xavfernandez]

There's a thing to be removed for pip 19.3 -- pip config --venv. Filing a PR for that.

#7163 took care of that.

Is there any other pull request / issue we would like to include in 19.3 ?

[xavfernandez]

And I'll need to be added as maintainer in PyPI.org 😛
(username: xafer)

[chrahunt]

#7072 is good to go, IMO. @xavfernandez, I'll leave it up to you whether we merge, since it would require regenerating AUTHORS.txt (+another hour waiting for CI).

[xavfernandez]

#7072 is good to go, IMO.

I'll include it then :)

I'll wait for monday morning to actually release 19.3 since I'll have very few available time tomorrow to deal with the potential aftermath of the release.

[pradyunsg]

@xavfernandez Sure!

I'll be online on Monday and Tuesday too, for sprints, so I will be hands-on-deck all day at that time.

[xavfernandez]

I still don't have the right to upload to PyPI. Who could add me to PyPI ? @pfmoore or @dstufft ?
Otherwise, I'll make the release PR and let @pradyunsg perform the upload ?

[pradyunsg]

Sounds like a plan to me. I can add you on PyPI. Lemme know whatever you prefer.

[pfmoore]

I've added you on PyPI

[pradyunsg]

@xavfernandez what's your PyPI username? xavfer is already added and has the same profile picture as you.

[pradyunsg]

That makes sense @pfmoore!

[pradyunsg]

@xavfernandez I'm at PyCon India Sprints. Lemme know when it's okay to start merging PRs filed by folks here. :)

[xavfernandez]

I've added you on PyPI

Thanks @pfmoore :)

I'm at PyCon India Sprints. Lemme know when it's okay to start merging PRs filed by folks here.

Feel free to merge the small ones: I'd first like #7198 to be merged before performing the release with it (if you could review #7198 by the way ;) ).
I see you are on IRC, I'll ping you when I'll create the release PR (around 12:00 UTC).

[xavfernandez]

19.3 has been released:

• Commit/tag is afcb3e7
• sdist & wheel are available: https://pypi.org/project/pip/19.3/
• get-pip.py is on its way (review needed): Update to 19.3 get-pip#51
• cpython has its PR bpo-38488: Upgrade bundled versions of pip & setuptools python/cpython#16782 (but the process there is unclear regarding news file & ticket...)

I'm currently waiting for get-pip.py to be updated to post on distutils-sig & discuss.python.org

[atugushev]

Thanks for the smooth release, folks! Excellent work! 🎉 🎉 🎉

[xavfernandez]

I merged my get-pip.py PR to be able to post the announcements on distutils-sig and discuss but a review is still welcome :)

I'll keep this issue open for the week in case there are unexpected fallouts.
In the meantime, feel free to merge pull requests, I'll use a maintenance branch if a 19.3.1 is needed.

[jayvdb]

Just noting #5599 is an issue effecting a lot of projects.

Maybe that issue should be pinned?

[pfmoore]

Pinning #5599 sounds like a reasonable suggestion - but I don't know how to do that.

Edit: Never mind, I found it.

[pradyunsg]

@xavfernandez FYI, I think we should probably do a bugfix release:

• Declaring 3.8 is explicitly supported: Declare support for Python 3.8 #7219 (comment)
• Fixing PEP 517 for packages that don't have a setup.py: Fix PEP 517 builds for packages without setup.py #6606

[xavfernandez]

#7232 is on its way.

[xavfernandez]

If #7232 brings no comment, I'll merge it and push the 19.3.1 tag, sdist & wheel tomorrow morning (UTC+2).

[pradyunsg]

Hurrah! Thanks @xavfernandez!

[xavfernandez]

19.3.1 has been released and get-pip.py updated (and fixed 🙄 )

[SASIN83]

i tried to upgrade pip but it says its a new version but when i check version it shows v10 pplz help

[pradyunsg]

@SASIN83 Please file a new issue: https://github.com/pypa/pip/issues/new/choose

[pradyunsg]

@xavfernandez hi hi, is there anything that needs to be done?

Are there bugs that were introduced that we'd want to fix in a bugfix release?

[xavfernandez]

None that I'm aware.
python/cpython#16782 still needs to be merged (or the way the vendoring is done changed), but nothing actionable on pip side.

[pradyunsg]

Hurray!

Thanks @xavfernandez for managing this release super smoothly. :)

Thanks to everyone else who's helped out either with direct code/docs/triage help or by participating in the discussions! :)