Release 22.0

[pradyunsg]

We're about three weeks out from a new year! I guess we'd want to cut a 22.0, given how full that milestone is. :)

[pradyunsg]

I can pick this up, although I won't be around during early Jan (I'm on vacation!); so the only time I would be able to do anything about these would be sometime in mid-Jan/late-Jan.

[pfmoore]

Sorry, I really don't want to commit to doing the January release, as I'm likely to be pretty busy. Hopefully I might have more free time later in the year to help out with the releases.

[mattip]

Is there a documented process to update _vendor? It would be nice to get packaging 21.0 -> 2.13.

[pfmoore]

It's covered in the documentation. However, I think we have a nox session for that - nox -s vendor.

We do a pass updating all of our vendored libraries just before a release anyway, so this should get caught then.

[uranusjr]

I won’t be around in earlier January either (actually will likely not be around starting from later December).

[pradyunsg]

Yea, and it should be possible to run the vendoring nox session with an upgrade flag, which automatically tries upgrading things; stopping when a failure occurs in the upgrade process.

[pradyunsg]

I'm gonna pre-emptively assign myself then. :)

If there's any concerns of any other committer wants to step up, just say so. :)

[pradyunsg]

these would be sometime in mid-Jan/late-Jan.

Cool, this is the plan for the release now.

[pradyunsg]

@pypa/pip-committers Okay, there's a few PRs that I'd like reviews on.

• Vendoring upgrade #10815
• Improve presentation of errors from subprocesses, during installation #10795
• Abort immediately on metadata generation failure instead of backtracking #10722

I think there's agreement on those ideas overall, but... more eyes, a proper review and an easy green tick 🤞🏽 would be much appreciated! I'm leaning toward merging those anyway tho, if there's no availability to do a review.

[pradyunsg]

Alrighty, looks like we're all set. I'll cut a release over the weekend. :)