#20578 2.20 release preparation Issue created by huonw 2.20.0 will be the next 'major' release. 2.19.0 was released on Jan 26, so a 6 week release spacing suggests a 2.20.0 close to March 8. For the previous few releases, I (@huonw) have been trying to keep an eye on (this isn't ordered): ☐ Get the code ready. This includes fixing issues and adding docs as required. • Triage incoming bugs and see if any are worth adding to the

2.20.x

milestone. • Semi-regularly check https://github.com/pantsbuild/pants/milestone/63 to have an understanding of what's blocking (and any others that are still open, e.g. an issue in 2.19.x might require fixing for 2.20.x). NB. we don't seem to have an explicit mechanism to indicate that something is a blocking issue. • Check/follow-up on #development on slack as required. ☐ Prepare release assets: • a

2.20.x.md

"what's new", similar to https://github.com/pantsbuild/pants/blob/main/src/python/pants/notes/2.19.x.md • a blog posts similar to pantsbuild/pantsbuild.org#134 ☐ Regular release candidate releases as usual (done by the MOTW, usually), and encourage people to test them ☐ Publish the release when ready ☐ When published, update example repos similar to #20526 (To be clear, usually others have done the work, but I've been trying to have the overview to see if anything falls through the cracks, and prompt things like "it seems like we're close to being ready".) pantsbuild/pants