Add some missing Release Notes entries #17245
Merged
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 release, we got some PRs made by external contributors from @gitstart π β¦ but we completely forgot to tell them at the time to add entries for their changes to the
RELEASE-NOTES.txtfile as part of their PR. So this PR adds the relevant entries:RELEASE-NOTES.txtfile (the one we expect contributors to update when they do a new PR to describe the changes, assuming those changes are interesting enough to end users to make it to the release notes)WordPress/{jetpack_,}metadata/release_notes.txtfiles that are usually auto-generated by our release tooling when it extracts the entries fromRELEASE-NOTES.txt. Since I already ran that tooling earlier today when I did the code freeze before adding those missing entries, I had to update those manually to simulate them being extracted from theRELEASE-NOTES.txtfile during code-freeze.PS: We need this PR to land ASAP so that our freelance writer can use those files (from
trunkonce they will have landed) to write nice editorialized copies for those entries, so we can then send that editorialized copy for release notes to translation this week.cc @vanessamaartinstt FYI as you might want to include those additional entries in the upcoming Call for Testing you'll likely be drafting today π