This is an automated email from the ASF dual-hosted git repository. royteeuwen pushed a commit to branch docs/release-management-finalize-website in repository https://gitbox.apache.org/repos/asf/sling-site.git
commit f28b23a27fb552a6fb2e8f01ae37ee529d445f3f Author: Roy Teeuwen <[email protected]> AuthorDate: Tue Aug 4 22:24:12 2026 +0200 Release docs: drop the JIRA version ordering step Nothing in the release process depends on the project's version order, and the CLI's finalize command performs the rest of the Update JIRA section. --- .../jbake/content/documentation/development/release-management.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/main/jbake/content/documentation/development/release-management.md b/src/main/jbake/content/documentation/development/release-management.md index 61ffd0b05..1a00df867 100644 --- a/src/main/jbake/content/documentation/development/release-management.md +++ b/src/main/jbake/content/documentation/development/release-management.md @@ -356,10 +356,10 @@ Go to [Manage Versions](https://issues.apache.org/jira/plugins/servlet/project-c Also create a new version X.Y.Z+2, if that hasn't already been done. -And keep the versions sorted, so when adding a new version moved it down to just above the previous versions. - Close all issues associated with the released version. +All of the above is performed by the Committer CLI's `finalize` command. See [Finalize](#4-finalize). + ## Update the Sling Starter Module If the new release should be included in the [Sling Starter](https://github.com/apache/sling-org-apache-sling-starter), please create PR after the artifacts are available on Maven Central. That usually happens within 60 minutes of the staging repository being closed.
