2.21 release preparation

[huonw]

2.21.0 will be the next 'major' release. 2.20.0 was released on Apr 16, so a 6 week release spacing suggests a 2.21.0 close to May 28.

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.21.x milestone.
  • Semi-regularly check https://github.com/pantsbuild/pants/milestone/64 to have an understanding of what's blocking (and any others that are still open, e.g. an issue in 2.20.x might require fixing for 2.21.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.21.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 Add 2.19.0 release blog post 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 Update example repositories to Pants 2.20 #20799

(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".)

Additional context

• This copies 2.20 release preparation #20578.
• See also Introduce a "stable release manager" process #20827

[cburroughs]

a blog posts similar to

I can do another emoji heavy entry if no one wants to take a stab at it.

2.21.0 will be the next 'major' release. 2.20.0 was released on Apr 16, so a 6 week release spacing suggests a 2.21.0 close to May 28.

I read the "six week" rule as the rc0s were a fixed number of weeks apart, not the final release. That is a late release would not trigger the next release being later --> having more stuff --> taking longer to go out --> repeat. So 2.21.0 can go out as soon as it feels "stable enough".

[huonw]

I can do another emoji heavy entry if no one wants to take a stab at it.

Fine by me, but feel free to solicit others too (I'll leave it in your hands unless I hear otherwise 😄 )!

I read the "six week" rule as the rc0s were a fixed number of weeks apart, not the final release. That is a late release would not trigger the next release being later --> having more stuff --> taking longer to go out --> repeat. So 2.21.0 can go out as soon as it feels "stable enough".

Ah, yes, I am unclear on the original intention but I think you may be right. I entirely agree with that cycle being a problem!

[huonw]

Opened #20970. Calling this done.

Thanks @cburroughs for the blog post!