diff options
| author | Marco Miller <marco.miller@ericsson.com> | 2020-09-30 15:14:05 -0400 |
|---|---|---|
| committer | Marco Miller <marco.miller@ericsson.com> | 2020-10-01 11:56:53 -0400 |
| commit | b8cdd2f1b168961e1b7a44699637a329a9e8f6bd (patch) | |
| tree | a4c1cfccb58e5d57b807ba6e7097ae87b47a884f | |
| parent | 9f76825d54473735f0b5ff88cc7255fafedea06c (diff) | |
Documentation: Mention adding changes to the release notes beside issues
Change-Id: Id845e07d0f95c8ab4c6f7c2af71bd198a8688654
| -rw-r--r-- | Documentation/dev-release.txt | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/Documentation/dev-release.txt b/Documentation/dev-release.txt index f99893e2aa..f0a80980c1 100644 --- a/Documentation/dev-release.txt +++ b/Documentation/dev-release.txt @@ -101,6 +101,9 @@ following the examples from the previous version notes. Add updated issue owners as reviewers of the uploaded change. More reviewers can be added or cc'ed, to further coordinate the final release contents. +Similarly to issues, also mention every noteworthy change done after the +previous release. Again, previous notes should be used as template examples. + You may need to split note update changes from the final change that updates the links. This allows non-final update changes to be reviewed and submitted timely. The final (links) change may take more time to complete, |