[meta] 11.2.0 and 10.5.0 release notes

Background information

• How to write a release note snippet
• Writing release notes for Drupal core releases

Release notes

• 11.2
  • 11.2.0 release notes draft gdoc
  • Issues tagged '11.2.0 release notes'
• 10.5
  • 10.5.0 release notes draft gdoc
  • Issues tagged '10.5.0 release notes'

Instructions

1. Read over the release notes draft. The section at the top is the initial outline for the release notes. The sections at the bottom need to be completed.
2. Make sure that all issues tagged '11.2.0 release notes' and '10.5.0 release notes' are included in the respective drafts.
3. If an issue is tagged for the 11.2.0 notes but not for the 10.5.0 notes, check whether it was backported and correct the tagging.
4. If an issue is tagged for the 10.5.0 release notes, ensure something was actually backported. Also ensure that the 10.4 version of the release note is accurate.
5. Review the format of the release notes, and leave comments on the Google doc where something seems incorrect:
   • Ensure that every release note describes a disruptive change. Additions without any disruptive changes belong in the release highlights post, not the release notes.
   • Ensure that every release note follows the release note snippet best practices.
   • Ensure that every release note (save those about a dependency update) includes a link to a change record.
   • Ensure that release notes are formatted correctly in bulleted lists, and that each list item has a blank newline between the tag and the list item text. For example:
     

                         <li>
                             A disruptive change is described here. For more information, review <a href="">the change record about what-and-such</a>.
                         </li>
                     

   • Follow the rough organization suggested by committers. If you think something belongs in a different section, leave a comment.
6. Use the Google Docs "suggestion" feature to suggest corrections, readability improvements, etc.
7. Comment on this issue to receive credit for working on the release notes.