Oh look! It's April again! (Release 20.1)

[pradyunsg]

As per our Release Cadence, it's release month!

Looking at the changes since 20.0.2, we do have quite a few changes and ~350 commits at this time. That seems to mean that there's more than enough work on master to justify a release. :)

---

We're in our beta period! We welcome users to provide us with feedback on the beta release. pip's beta release can be installed by running:

python -m pip install --upgrade --pre pip

[pradyunsg]

Following on from #7531 (comment), I'm happy to be the release manager for this release as well.

I promise to clean my build directory this time -- there's automation that will force me to anyway. :)

[atugushev]

Hello @pradyunsg! Any ETA?

[brainwane]

@atugushev There are some discussions maintainers probably need to have over the next few days -- I think we'll probably have an estimated date after that, but I would be surprised if we could get the release out in the first half of the month. Are you waiting for anything in particular?

[pradyunsg]

In terms of a timeline for this release, as of right now, I'm thinking of making a beta release on Monday, 20th April. This would give us the opportunity to iron out any kinks in our beta process prior to needing to use it for the resolver rollout in our next release cycle.

I'm still undecided on the length of the beta, but it'll definitely be at least 7 days.

@pypa/pip-committers Feel free to keep merging PRs as usual till April 13th (coming Monday). After April 13th, please let me know about PRs you'd like to merge before merging PRs. :)

[deveshks]

Hi @pradyunsg

Is the directive mentioned in the comment above, also applicable for folks who don't have explicit merge access as well?

[pradyunsg]

No. After April 13th, I'd like to be in-the-loop of, and significantly reduce the number of, PRs that myself and other committers merge until after the release is done.