lukaszlenart commented on code in PR #1844: URL: https://github.com/apache/struts/pull/1844#discussion_r3782758361
########## .claude/skills/releasing-struts/release-runbook.md: ########## @@ -0,0 +1,262 @@ +# Release Runbook + +The commands, in order. [`SKILL.md`](SKILL.md) holds the sequence, the gates and the judgement; +this file is what you type. + +**Provenance.** Everything marked ✔ was verified against the repository, a completed release +(7.3.0 / 6.11.0, August 2026), or the release manager's scripts. Everything marked +**⚠ unverified** is carried over from the 2017 cwiki page and has *not* been confirmed against a +current run — check it before relying on it, and correct this file when you do. + +**The scripts.** Phases 3 and 5 ship with this skill, in [`scripts/`](scripts): + +| Script | Phase | What it does | +|---|---|---| +| [`stage-assemblies.sh`](scripts/stage-assemblies.sh) | 3 | Closed staging repo → `dist/dev`, renamed and re-hashed | +| [`promote-dist.sh`](scripts/promote-dist.sh) | 5 | `dist/dev` → `dist/release` | + +Both take `$VERSION` from the environment and refuse to run without it. They are ports of the +release manager's local toolbox (`~/Projects/Apache/minatour/bin/`), unchanged in behaviour +apart from `set -eu`, the `$VERSION` guard, tolerant hash cleanup and an explicit svn commit +message — each deviation is listed in the script's own header. + +A third script in that toolbox, `update-struts2-draft-docs.sh`, exports Confluence into the +retired svn production site. **It is dead and is deliberately not ported.** Do not run it. + +--- + +## Phase 1 — Prepare + +✔ Two lines, two releases: + +| Line | Branch | Build check that must pass | +|---|---|---| +| 7.x | `main` | `Build and Test (JDK 17)` | +| 6.x | `support/struts-6-x-x` | `Build and Test (8)` | + +Both branches are protected in `.asf.yaml` and must be green before you start. + +```bash +git checkout main && git pull --ff-only +mvn clean install -DskipAssembly Review Comment: It would be good to check on which version of JDK we are before running the build - if version is wrong, let's ask user what to do or how to switch to proper JDK version. Each local env can be configured in different way, user-specific way -- 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]
