royteeuwen opened a new pull request, #286: URL: https://github.com/apache/sling-site/pull/286
Follows apache/sling-org-apache-sling-committer-cli#40, which makes the Committer CLI's `finalize` command update the website as its last step. ### Finalize section Documents the website step instead of telling the release manager to do it afterwards, and describes how downloads entries are matched: on the **artifact id** rather than the module's display name (the two often differ — *Tracer* is listed as *Log Tracer*), and only for entries on the **same major version**, so a maintenance release of an older line never downgrades the page. Also notes that the news page stays manual, via `update-news`, and how to resume `finalize` by release name after promotion. ### Promoting the Release section Two corrections to the manual instructions: - The downloads page needs updating for **every** release, not only for new modules. Every non-bot commit to the site over the last ten months updates `releases.md` and `downloads.tpl` together; the renovate app is a lagging backstop rather than the primary path (PR #221 was open from September 2025 to April 2026). - The page lists only the **most recent major version** of a module, even when older majors are still distributed, so a maintenance release of an older major normally has nothing to update there. Also notes which of these steps the CLI now performs, and that the site's own build and deploy delay already covers most of the CDN wait. ### Update JIRA section Drops the "keep the versions sorted" step — nothing in the release process depends on the project's version order — and points at `finalize`, which performs the rest of that section. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
