[jira] [Commented] (SLING-13253) Automate Apache Sling post-vote release steps in the committer CLI

["Roy Teeuwen (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-13253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18105690#comment-18105690 ] 

Roy Teeuwen commented on SLING-13253:
-------------------------------------

Implemented in the committer CLI. What landed:

* apache/sling-org-apache-sling-committer-cli#47 - upgrade JGit to 7.7.1 (the 5.13.x line has no shallow clone support; JGit 7 additionally needs commons-codec in the feature and java.management in the jlink'd JRE, without which the bundle silently fails to resolve)
* apache/sling-org-apache-sling-committer-cli#40 - finalize updates the Sling website as its last step: the releases list and the downloads page, committed and pushed to sling-site. Downloads entries are matched on the artifact id rather than the display name (the two often differ - Tracer is listed as Log Tracer) and only within the same major version, so a maintenance release of an older line cannot downgrade the page. A separate release update-news command announces a release on the news page; it is deliberately not part of finalize.
* apache/sling-org-apache-sling-committer-cli#50 - fixes found running the update for real: the published branch is checked out explicitly before resetting, the release manager is recorded as committer as well as author, and an entry already at the released version is no longer reported as missing.
* apache/sling-org-apache-sling-committer-cli#48 - the site checkout is cloned shallow and single-branch (~25MB rather than ~380MB), and the shallow fetch is only requested for a checkout that is already shallow so a full clone is never truncated.
* apache/sling-site#286 - the release management documentation updated accordingly.

Verified against a real past release: replaying Event Impl 4.4.2 against a checkout reverted to its pre-release state produced a downloads.tpl byte-identical to the commit that released it, pushed from a shallow clone.

Not automated, deliberately: the news page (only releases worth announcing get an entry), the announcement email, and the Sling Starter inclusion PR.

> Automate Apache Sling post-vote release steps in the committer CLI
> ------------------------------------------------------------------
>
>                 Key: SLING-13253
>                 URL: https://issues.apache.org/jira/browse/SLING-13253
>             Project: Sling
>          Issue Type: New Feature
>          Components: Tooling
>            Reporter: Roy Teeuwen
>            Assignee: Roy Teeuwen
>            Priority: Major
>             Fix For: Committer CLI 1.0.0
>
>
> The sling-cli tool currently helps with pre-vote steps. This adds the post-vote release automation so a release manager can drive the whole flow from the CLI: list open staging repositories, close staging, promote/drop after a vote, tally votes (PMC-aware), update dist.apache.org, and a one-step finalize.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)