#20964 2.22.0 release prep Issue created by huonw 2.22.0 will be the next 'major' release. 2.21.0 was released on May 28, so a 6 week release spacing suggests 2.22.0 close to July 9. 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.22.x

milestone. • Semi-regularly check

the 2.22.x milestone that hasn't been created yet

to have an understanding of what's blocking (and any others that are still open, e.g. an issue in 2.21.x might require fixing for 2.22.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: • make sure

2.22.x.md

"what's new" makes sense and some highlights called out (it's been added to incrementally, so maybe an over-view editing pass would be good) • 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 #20799 Additional context • This copies #20846. • See also #20827 pantsbuild/pants