[wu-sheng]

Running scripts/release.sh for 0.15.0 ended like this, and it was not clear what to do next or in which order:

+ echo 'Make sure you have released the GitHub release, updated the events, download links and menus?'
Make sure you have released the GitHub release, updated the events, download links and menus?
+ read -r _

Run the script from the skywalking-cli checkout of the release tag. It now:

1. Runs the svn mv to dist/release, or skips it when the packages are already there, so you can rerun the script to finish the other steps.
2. Asks Publish the GitHub release <v> ...? [y/N], then runs gh release create. The notes are the version's section of CHANGES.md, read from the tag. It skips this step when the release already exists.
3. Asks Build and push docker.io/apache/skywalking-cli:<v> and :latest ...? [y/N], then runs make docker.push. It skips this step when the image is already on Docker Hub, or when the checkout is not at the tag.
4. Lists each step as done, already done, skipped or failed. If any step was skipped or failed, it says to rerun the script.
5. Reminds you to update the website and add the release on reporter.apache.org. It prints the announcement email with its subject and recipients, and fixes the dev@skywalkiing.apache.org typo.
6. Asks Remove the older releases 0.13.0 0.14.0 from dist/release? [y/N], then runs svn rm.

The script no longer traces every command (set -x). It prints each command just before running it. The Publish section of the release guide describes the new flow.

Tests

The tests stub svn, gh, docker, make and git.

• They pass on macOS (sh, bash, dash: 66 of 66) and on Linux golang:1.26 (dash with mawk, and bash: 44 of 44). They cover:
  • all answers yes;
  • packages already in dist/release (no svn mv);
  • all answers no;
  • stdin closed;
  • GitHub release and image already published (neither is asked);
  • checkout not at the tag (no Docker question);
  • gh or make docker.push failing (the rest still runs, and the summary says to rerun);
  • svn mv failing (the script stops);
  • no CHANGES.md section, svn ls failing, no older releases, svn rm failing, and VERSION unset.
• With real git at tag 0.15.0, on macOS and Linux, the GitHub release notes match the 0.15.0 section of CHANGES.md exactly, and the Docker step runs because the checkout is at the tag.
• shellcheck reports nothing.