jerryshao opened a new issue, #10478:
URL: https://github.com/apache/gravitino/issues/10478
### What would you like to be improved?
The Gravitino release process is complex, multi-staged, and error-prone when
done manually. There is no structured tooling to guide a release manager
through the full pipeline step by step, track stage completion, or handle
resumption after failures.
### How should we improve?
Add a `gravitino-release` Claude Code skill
(`dev/release/gravitino-release/SKILL.md`) that acts as an interactive release
manager agent. The skill:
- Guides the release manager through all 7 stages in order: **tag → build →
docs → publish → docker → finalize → release-note**
- Tracks stage completion via `.done` state files (anchored to the script
directory, not the working directory)
- Supports **mock mode** (using `dev/release/mock/`) and **dry-run mode**
for safe testing without real operations
- Runs preflight checks (open PRs, CI status) before tagging
- Collects and validates all required credentials before each stage
- Guards the irreversible `finalize` stage with explicit confirmation
- Generates release notes from GitHub issues labelled with the release
version
Also fixes two bugs in the release scripts:
- `do-release.sh` and `mock/do-release.sh`: `STATE_DIR` used a relative path
(`.release-state`) causing state files to be written to the caller's working
directory instead of alongside the scripts. Fixed to use `$SELF/.release-state`.
- `mock/do-release.sh`: log files also used a relative path; fixed to use
`$SELF/${STEP}.log`.
--
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]
