doc: release: drop the notes about listing github issues

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 <[email protected]>
bkietz · Jul 25, 2023 · ecf29a7 · ecf29a7
1 parent a2395e8
commit ecf29a7
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 30 deletions.
diff --git a/doc/project/release_process.rst b/doc/project/release_process.rst
@@ -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 <[email protected]>
-
-    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.
diff --git a/doc/releases/release-notes-3.5.rst b/doc/releases/release-notes-3.5.rst
@@ -313,11 +313,5 @@ Documentation
 Tests and Samples
 *****************
 
-Issue Related Items
-*******************
-
 Known Issues
-============
-
-Addressed issues
-================
+************