patrick/zephyr
1
0
Fork 0
Code Issues Pull requests Actions 8 Packages Projects Releases Wiki Activity

doc: release: drop the notes about listing github issues

Browse source 
Drop the notes about listing all the github issues with the release
notes. That was a huge list of github issues sorted by closing time,
very noisy and hard to maintain.

The unfiltered list of changes is already in the commit history, a
distilled list is now in the blog posts and a final list is in the notes
summary.

The issue list has been skipped in 3.4 already, let's just drop it from
the process.

Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
This commit is contained in:
Fabio Baltieri 2023-07-21 11:51:14 +00:00 committed by Carles Cufí
parent a2395e8d5b
commit ecf29a77f8
2 changed files with 1 additions and 30 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
doc/project/release_process.rst
View file

@ -409,26 +409,3 @@ steps:
#. Send an email to the mailing lists (``announce`` and ``devel``) with a link
to the release
Listing all closed GitHub issues
=================================
The release notes for a final release contain the list of GitHub issues that
have been closed during the development process of that release.
In order to obtain the list of issues closed during the release development
cycle you can do the following:
#. Look for the last release before the current one and find the day it was
tagged::
$ git show -s --format=%ci v1.10.0
tag v1.10.0
Tagger: Kumar Gala <kumar.gala@linaro.org>
Zephyr 1.10.0
2017-12-08 13:32:22 -0600
#. Use available release tools to list all the issues that have been closed
between that date and the day of the release.

8
doc/releases/release-notes-3.5.rst
View file

@ -313,11 +313,5 @@ Documentation
Tests and Samples
*****************
Issue Related Items
*******************
Known Issues
============
Addressed issues
================
************