Initial sketch of what's new in 2.18 (Cherry-pick of #19999) #20147
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This sketches (in rather extensive detail...) a "what's new" file for 2.18, up to https://github.com/pantsbuild/pants/commits/bd28f12623a57313486f9d2f834c0e78051aa8a7/ (bd28f12...2.18.x is what's happened since then).
This basically lists everything from all the GitHub Releases, in human form, because I don't think there's another way for a user to get a sense of what's included in a single place.
I'm hoping we can do a quick pass here, and then iterate once it's in, because there's so many sections that different people will know best about, rather than having to gate it all through me (as the author of this PR).
A downside of this current framing is that it doesn't emphasise the breaking changes (user API changes) very well.