This is an automated email from the ASF dual-hosted git repository.

pkarwasz pushed a commit to branch doc/update-lifecycle-information
in repository https://gitbox.apache.org/repos/asf/logging-parent.git

commit 5a006b5fa804d2ffb45f56288128ddf7b07aaf51
Author: Piotr P. Karwasz <[email protected]>
AuthorDate: Mon Dec 8 12:22:10 2025 +0100

    Update lifecycle information upon release
    
    This update enhances the release instructions by adding a reminder for 
release managers to review and update end-of-maintenance dates as part of the 
release process.
---
 .../antora/modules/ROOT/pages/release-instructions-project.adoc     | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git 
a/src/site/antora/modules/ROOT/pages/release-instructions-project.adoc 
b/src/site/antora/modules/ROOT/pages/release-instructions-project.adoc
index 5ff3eef..f7e1c0a 100644
--- a/src/site/antora/modules/ROOT/pages/release-instructions-project.adoc
+++ b/src/site/antora/modules/ROOT/pages/release-instructions-project.adoc
@@ -67,7 +67,11 @@ For instance, `site-project.version` needs to be updated for 
`logging-parent`.
 ----
 ./mvnw -N -P changelog-release
 ----
-.. Edit the release notes (i.e., `src/changelog/7.8.0/.release-notes.adoc.ftl`)
+.. Open the generated release-notes template 
(`src/changelog/<version>/.release-notes.adoc.ftl`) and summarize the key 
user-visible changes for this release (e.g., new features, behavioral changes, 
significant bug fixes).
+.. Inspect all files under `src/changelog/<version>/` and ensure the entries 
accurately reflect what users need to know.
+In particular, ensure that all user-visible changes are documented and that no 
internal-only changes are included (e.g., test-only changes, test dependency 
updates, documentation updates, etc.).
+.. Review the changelog (i.e., `src/changelog/7.8.0/`) to ensure all changes 
pertinent to the user and only those are included (e.g., exclude documentation 
updates, test dependencies bumps, etc.).
+.. In case this is **not** a patch release, ensure that the end-of-maintenance 
dates of the previous releases is updated.
 
 . Commit & push your changes:
 +

Reply via email to