Hi David, Could you please, for future releases, try to stay close to the release template from [0], namely provide the JIRA release name(s) in the subject field? You then don’t have to name the artifacts, the list of JIRA versions would be enough.
Robert and I worked on this tool to help with most of the manual release tasks [1]. Although not complete, it automates a lot of the steps [1] one needs to perform when starting or promoting a release, including sending emails. Thanks, Radu [0] - https://sling.apache.org/documentation/development/release-management.html#starting-the-vote <https://sling.apache.org/documentation/development/release-management.html#starting-the-vote> [1] - Usage: docker run -it --env-file=./docker-env apache/sling-cli release [COMMAND] Performs release-related operations Commands: create-new-jira-version Creates a new Jira version, if needed, and transitions any unresolved issues from the version being released to the next one list Lists all open releases prepare-email Prepares an email vote for the releases found in the Nexus staged repository tally-votes Counts votes cast for a release and generates the result email update-local-site Updates the Sling website with the new release information, based on a local checkout update-reporter Updates the Apache Reporter System with the new release information help Displays help information about the specified command
