From 2944a0a7fc67725b90af4b628485b77300b35791 Mon Sep 17 00:00:00 2001 From: mikecarper Date: Sat, 24 Oct 2026 19:34:34 -0700 Subject: [PATCH] Keep the complete feature list only in the release guide --- RELEASE.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index b0d319e1e..4637fe56e 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -91,13 +91,16 @@ Use the same format for each revision: 6. **Tested and limitations:** separate build checks from physical tests. Name important remaining limitations and link source-specific evidence. -Include a collapsed **Features beyond mainline MeshCore** section with simple, -linked bullets for the complete feature overview. Name the compared upstream +In the hosted release guide, include a collapsed +**Features beyond mainline MeshCore** section with simple, linked bullets for +the complete feature overview. Name the compared upstream release and comparison date; distinguish additions from extensions of existing features, and qualify board/role support. Keep it separate from the revision's New and Fixed lists. Recheck it against the actual released source each time. Put a direct feature link at the top of every release page. Link to the hosted release guide's `#extra-features` disclosure so clicking opens the feature list. +Keep the complete list in that guide; do not duplicate the dropdown in GitHub +release bodies. Compare the actual previous release's source and notes. A long commit list can include old work imported by merges; do not present it all as new. Do not relist