Background information
Release notes
- #3409180: 10.3.0-alpha1 release notes
- #3409181: 10.3.0-beta1 release notes
- #3409182: 10.3.0-rc1 release notes
- 10.3.0 release notes draft gdoc
Instructions
- Read over the 10.3.0 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.
- Make sure that all Issues tagged '10.3.0 release notes are included in the release notes.
- 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.
- Use the Google Docs "suggestion" feature to suggest corrections, readability improvements, etc.
- Comment on this issue to receive credit for working on the release notes.
