-
-
Notifications
You must be signed in to change notification settings - Fork 606
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.21 release preparation #20846
Comments
I can do another emoji heavy entry if no one wants to take a stab at it.
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". |
Fine by me, but feel free to solicit others too (I'll leave it in your hands unless I hear otherwise 😄 )!
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! |
Opened #20970. Calling this done. Thanks @cburroughs for the blog post! |
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):
2.21.x
milestone.2.21.x.md
"what's new", similar to https://github.com/pantsbuild/pants/blob/main/src/python/pants/notes/2.19.x.md(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
The text was updated successfully, but these errors were encountered: