You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@roller.apache.org by sn...@apache.org on 2026/09/11 21:24:25 UTC
(roller) 01/01: Add a roller-release developer skill documenting the release procedure
This is an automated email from the ASF dual-hosted git repository.
snoopdave pushed a commit to branch add-roller-release-skill
in repository https://gitbox.apache.org/repos/asf/roller.git
commit cfe93116bec04390c492692f1f21b918ab4846a6
Author: David M. Johnson <sn...@apache.org>
AuthorDate: Thu Sep 10 16:36:54 2026 -0400
Add a roller-release developer skill documenting the release procedure
Adds an optional skills/ directory holding written-down project procedures
for Roller developers, starting with the release workflow: preparing and
versioning a candidate, building, signing, verifying, staging, voting,
promoting the approved bytes, updating the website and announcing.
The skill is plain Markdown plus two helper scripts. It is not part of the
build, the runtime, or the source and binary distributions; the source
assembly's include list does not cover this directory. Developers who use an
agent tool can symlink it under .claude/skills/, and everyone else can read
it as documentation. See skills/README.md.
The helpers preview by default and never commit, tag, push, sign or send
mail. The skill records procedure only; the PMC owns release decisions and
ASF policy governs what a release requires.
Claude-Session: https://claude.ai/code/session_015X69HHQ5XnjRkJP8ymzwFf
---
skills/README.md | 66 +++++++
skills/roller-release/SKILL.md | 95 ++++++++++
skills/roller-release/references/asf-policy.md | 45 +++++
skills/roller-release/references/atr.md | 36 ++++
skills/roller-release/references/dist-svn.md | 59 ++++++
skills/roller-release/references/signing-key.md | 54 ++++++
.../roller-release/references/vote-and-announce.md | 76 ++++++++
skills/roller-release/references/website.md | 39 ++++
skills/roller-release/scripts/bump-version.sh | 68 +++++++
skills/roller-release/scripts/check-release.sh | 205 +++++++++++++++++++++
10 files changed, 743 insertions(+)
diff --git a/skills/README.md b/skills/README.md
new file mode 100644
index 000000000..45c082ac2
--- /dev/null
+++ b/skills/README.md
@@ -0,0 +1,66 @@
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+ https://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+# Roller developer skills
+
+Optional developer tooling. Nothing here is part of the Roller build, the
+source or binary distributions, or the runtime; the source assembly does not
+include this directory. You can ignore it entirely and work on Roller normally.
+
+Each subdirectory is a "skill": a `SKILL.md` describing a project procedure,
+plus supporting reference notes, templates and helper scripts. They exist so
+that recurring project chores are written down in one reviewable place instead
+of living in one committer's head.
+
+| Skill | Covers |
+|---|---|
+| [`roller-release`](roller-release/SKILL.md) | Preparing, building, signing, verifying, staging, voting on and publishing a release, plus the release website and announcement drafts. |
+
+## Reading them
+
+`SKILL.md` and the files under `references/` are plain Markdown. Read them
+directly for a written account of how a release is put together. No tooling is
+required for this.
+
+## Using them with an AI coding assistant
+
+The layout follows the convention used by Claude Code and similar agent tools,
+which discover skills under `.claude/skills/`. To make them available without
+duplicating the files:
+
+```sh
+mkdir -p .claude/skills
+ln -s ../../skills/roller-release .claude/skills/roller-release
+```
+
+`.claude/` is not tracked by this repository, so this is a local choice that
+affects only your checkout. Copying the directories instead of symlinking works
+equally well.
+
+## Scope and limits
+
+These skills describe procedure; they do not grant authority. The PMC owns
+release decisions, and ASF policy governs what a release requires. Where a skill
+and current ASF policy disagree, policy wins and the skill needs fixing.
+
+The helper scripts under `scripts/` are deliberately conservative: they preview
+by default, they do not commit, tag, push, sign on your behalf, or send mail,
+and they are not a substitute for reading the diff and verifying a candidate
+yourself. Verify current ASF policy from its authoritative sources rather than
+trusting a summary here.
+
+Corrections are welcome as ordinary pull requests.
diff --git a/skills/roller-release/SKILL.md b/skills/roller-release/SKILL.md
new file mode 100644
index 000000000..43ca49ec2
--- /dev/null
+++ b/skills/roller-release/SKILL.md
@@ -0,0 +1,95 @@
+---
+name: roller-release
+description: Prepare, build, sign, verify, stage, vote on and publish Apache Roller releases, including release website updates and announcement drafts.
+---
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+ https://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+# Apache Roller releases
+
+Use the current checkout, project release decisions and
+[ASF policy sources](references/asf-policy.md). Keep release execution notes,
+personal signing setup and undisclosed security scope outside this skill.
+Loading the skill does not authorize sending mail, pushing tags or publishing.
+
+## Establish release inputs
+
+Record the source checkout, target branch and exact commit; release version;
+RC number and tag; release-manager ASF ID; signing-key fingerprint; distribution
+working copies; and website checkout. Supply these from the actual release,
+not defaults from an earlier session. Use a clean tree or isolated checkout.
+
+Check build documentation and CI for the branch's supported JDK. Confirm Maven,
+GnuPG, SVN and archive tools are available. Python 3 is used by the version helper.
+Use [signing-key guidance](references/signing-key.md) before building a candidate.
+
+## Prepare and verify
+
+1. Agree scope and version, keeping undisclosed vulnerability details private.
+2. Inspect version-bearing POMs and packaging scripts. Run
+ `scripts/bump-version.sh <old> <new>` from this skill for a preview; use
+ `--write` only to apply the reviewed scope. It does not commit. Update release
+ notes and other appropriate references manually, preserving historical entries.
+3. Commit the release inputs and record an RC tag at the exact source revision.
+ Build from that revision so the embedded revision matches the candidate.
+ Preserve candidate history; changed artifacts normally require a new candidate
+ and vote. Do not silently replace artifacts already being voted on.
+4. Build and test from the root using the branch's documented Maven invocation
+ (normally `mvn -V -ntp clean install`). Build `assembly-release` separately
+ with `mvn -f assembly-release/pom.xml package`; it is outside the root reactor.
+5. Inspect the source and binary tar/zip archives. Sign and generate checksums
+ using [signing instructions](references/signing-key.md).
+6. Run `scripts/check-release.sh <artifact-dir>` from this skill. Its optional
+ `--build` compiles the source archive with tests skipped; it does not replace
+ the test suite, a full license review, or independent voter verification.
+7. Stage and download the candidate using [distribution guidance](references/dist-svn.md).
+ Verify signatures, checksums, contents and source build from the downloaded files.
+
+## Vote and publish
+
+Use [vote and announcement templates](references/vote-and-announce.md). Normally
+allow at least 72 hours and require at least three positive binding votes and
+more positive than negative binding votes. Check current policy for exceptions.
+Record the result and the exact approved candidate.
+
+Promote the approved artifact bytes; do not rebuild. If filenames lose the RC
+suffix, detached signatures still verify those unchanged bytes, but checksum
+filenames must be updated and verified. Point the final Git tag at the approved
+RC commit. Inspect remote destination paths before distribution changes.
+
+Update and publish the [website](references/website.md), verify public download
+links and propagation, then announce. Prune superseded distributions only after
+the website points to the new release and archive availability is confirmed.
+Keep historical signing keys available for verification of old releases.
+
+For security releases, coordinate advisory timing with the PMC and ASF Security;
+use the companion `roller-security` skill when available. Public vote material
+must not expose undisclosed case details. The operator upgrade must be available
+when the advisory is published.
+
+## References and helpers
+
+- [ASF policy](references/asf-policy.md): authoritative sources and review boundaries.
+- [Signing](references/signing-key.md): explicit signer selection and verification.
+- [Distribution](references/dist-svn.md): staging, promotion and pruning.
+- [Vote and announcement](references/vote-and-announce.md): reusable message drafts.
+- [Website](references/website.md): source edits, rebuild and link verification.
+- [Release tooling](references/atr.md): evaluating Apache Trusted Releases.
+
+Resolve helper paths relative to this skill; when using the repository copy,
+they are under `skills/roller-release/scripts/`. Helpers do not commit or publish.
diff --git a/skills/roller-release/references/asf-policy.md b/skills/roller-release/references/asf-policy.md
new file mode 100644
index 000000000..2adca93d0
--- /dev/null
+++ b/skills/roller-release/references/asf-policy.md
@@ -0,0 +1,45 @@
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+ https://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+# Authoritative release policy
+
+Consult these sources when cutting a release; this skill is not a policy snapshot:
+
+- [Release policy](https://www.apache.org/legal/release-policy.html): source artifacts,
+ binding vote requirements, licensing and publication.
+- [Distribution policy](https://infra.apache.org/release-distribution.html): official
+ distribution channels, signatures, digests, download links and archive handling.
+- [Release signing](https://infra.apache.org/release-signing.html): key and signature guidance.
+- [Release publishing](https://infra.apache.org/release-publishing.html): operational steps.
+- [Roller release process](https://cwiki.apache.org/confluence/spaces/ROLLER/pages/75651/Release+Process):
+ project instructions; verify paths and commands against the current checkout.
+
+A source release is the approved artifact; binary packages are convenience
+artifacts. Release approval requires at least three positive binding votes and
+more positive binding votes than negative ones. The normal review period is at
+least 72 hours; consult the policy for exceptional expedited releases.
+
+Independently validate signed source packages, compile and test them, and review
+licensing. `check-release.sh` checks selected mechanical properties only. Presence
+of LICENSE and NOTICE does not prove that bundled material is correctly licensed.
+Inspect compiled artifacts, third-party content and exclusions in the actual
+source archive. Do not treat a historical release as an exemption from policy.
+
+Publish the artifacts that were approved. Rebuilding changes what voters reviewed
+and requires renewed approval. Use the official channels and verify public links
+before announcing availability. Keep per-release findings and corrective actions
+in release notes or the private coordination workspace as appropriate, not here.
diff --git a/skills/roller-release/references/atr.md b/skills/roller-release/references/atr.md
new file mode 100644
index 000000000..328c6b4c6
--- /dev/null
+++ b/skills/roller-release/references/atr.md
@@ -0,0 +1,36 @@
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+ https://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+# Evaluating Apache Trusted Releases
+
+[Apache Trusted Releases](https://releases.apache.org) is an alternative release
+workflow to evaluate with the PMC. Check its current documentation, availability,
+project enrollment and supported packaging before adoption; this skill does not
+pin a platform status or participating-project list.
+
+Try a non-publishing rehearsal and establish how the chosen tool handles:
+
+- Source and convenience binary archives, signatures and checksums.
+- Existing project distribution layout and KEYS handling.
+- Candidate identity, vote evidence, cancellation and replacement.
+- Promotion of the exact approved bytes and website coordination.
+- Access control and the separation of private security coordination from
+ public release artifacts and messages.
+
+Agree the workflow and ownership before a release deadline. Keep the evaluation
+and any per-release decision in project planning records. Do not switch an active
+release between tools without reconciling candidate identity and approval evidence.
diff --git a/skills/roller-release/references/dist-svn.md b/skills/roller-release/references/dist-svn.md
new file mode 100644
index 000000000..25af16340
--- /dev/null
+++ b/skills/roller-release/references/dist-svn.md
@@ -0,0 +1,59 @@
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+ https://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+# Distribution staging and promotion
+
+Confirm the current project layout before preparing paths:
+
+```sh
+svn ls https://dist.apache.org/repos/dist/dev/roller/
+svn ls https://dist.apache.org/repos/dist/release/roller/
+```
+
+The conventional layout is `roller-<major.minor>/v<version>/` below each project
+root. RC suffixes are typically in archive filenames. Verify this convention for
+the target branch; do not infer paths from an older wiki example.
+
+Use separate user-selected working directories for dev and release SVN checkouts.
+Stage only the intended candidate archives and signature/checksum sidecars. Review
+`svn status` and `svn diff` before committing. Download staged files to a fresh
+directory and verify them before starting the vote. Development staging is publicly
+accessible even though it is not an official release; do not upload private notes.
+
+## Approved-candidate promotion
+
+Record the passed vote, source SVN revision, candidate filenames and destination.
+Use an SVN working copy or a single reviewed repository transaction to promote
+only that candidate. Preserve archive bytes and detached signatures. If removing
+an RC suffix from filenames, update the filename references in checksum sidecars
+and verify each digest against the unchanged archive.
+
+Do not blindly promote everything in a version directory: it may contain cancelled
+candidates or unrelated files. Verify the final inventory, signature fingerprints
+and checksum checks after promotion. Never rebuild to remove an RC suffix.
+
+Wait for distribution propagation and check the public download URLs, not merely
+SVN success. Follow the current
+[release publishing guidance](https://infra.apache.org/release-publishing.html)
+for timing. Update the website and verify its links before announcing.
+
+## Cleanup
+
+Remove cancelled candidate files only within the agreed cleanup scope, checking
+exact filenames first. For superseded official releases, confirm archive
+availability and update website links before pruning. Preserve the KEYS history.
+A successful delete does not remove copies already downloaded from public staging.
diff --git a/skills/roller-release/references/signing-key.md b/skills/roller-release/references/signing-key.md
new file mode 100644
index 000000000..27fe1677e
--- /dev/null
+++ b/skills/roller-release/references/signing-key.md
@@ -0,0 +1,54 @@
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+ https://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+# Release signing
+
+Read the current [ASF signing guidance](https://infra.apache.org/release-signing.html)
+and [distribution policy](https://infra.apache.org/release-distribution.html).
+Select the acting release manager's key explicitly. Never copy another person's
+fingerprint or assume the default local key is suitable.
+
+Check ownership, expiry, revocation, algorithm and strength, including the signing
+subkey. For a new RSA signing key, use at least 4096 bits and an appropriate ASF
+identity. Keep private keys, passphrases, keyring inventories and local configuration
+backups outside the checkout. Let GnuPG prompt through the user's normal pinentry;
+do not capture a passphrase in shell commands or agent output.
+
+Publish the public key through the project's KEYS process and the release manager's
+ASF profile as applicable. The project KEYS file is available at
+<https://downloads.apache.org/roller/KEYS>. Add new public keys without removing
+historical signing keys. Verify fingerprints independently before trusting an import.
+
+Set `ROLLER_SIGNING_KEY` to the selected fingerprint and `VERSION` / `RC_SUFFIX`
+to the release inputs. Inspect the checkout's `assembly-release/sign-release.sh`
+usage; in versions supporting positional inputs, run from the repository root:
+
+```sh
+assembly-release/sign-release.sh "$VERSION" "$RC_SUFFIX"
+```
+
+The current script expects `ROLLER_SIGNING_KEY` in its environment. Export it
+explicitly in the release session. Confirm that the script signs with the intended
+key and uses an approved digest. Do not transplant an old signing script from
+release notes. Generate armored detached signatures and SHA-256 and/or SHA-512
+checksum sidecars; avoid legacy digest formats.
+
+Verify every archive's signature against its bytes and every checksum from the
+artifact directory. Check the expected fingerprint, not just GnuPG's exit status.
+A cryptographically valid signature does not itself establish signer identity or
+full release compliance. Keep the signer fingerprint in release execution notes
+and the vote draft, not as a fixed default in this skill.
diff --git a/skills/roller-release/references/vote-and-announce.md b/skills/roller-release/references/vote-and-announce.md
new file mode 100644
index 000000000..512a69f72
--- /dev/null
+++ b/skills/roller-release/references/vote-and-announce.md
@@ -0,0 +1,76 @@
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+ https://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+# Vote and announcement drafts
+
+Replace bracketed values from the actual release record. Verify URLs, tag commit,
+artifact checksums and signer fingerprint. Do not send messages merely because a
+template has been filled. Keep undisclosed security characterization out of public
+vote threads and release notes before coordinated announcement.
+
+## Vote
+
+Subject: [VOTE] Release Apache Roller [version] ([candidate])
+
+Please review and vote on Apache Roller [version], candidate [candidate].
+
+Source and convenience binary artifacts: [staging URL]
+Source tag: [tag URL and commit]
+KEYS: https://downloads.apache.org/roller/KEYS
+Signing fingerprint: [release manager's verified fingerprint]
+Release notes: [appropriate public release notes URL]
+
+The vote will remain open until at least [date, time and timezone], allowing
+at least 72 hours for review under the normal process.
+
+[ ] +1 Release this candidate
+[ ] +0 No opinion
+[ ] -1 Do not release, because [reason]
+
+[Release manager name]
+
+## Result
+
+Subject: [RESULT][VOTE] Release Apache Roller [version] ([candidate])
+
+The vote [passed/did not pass].
+
+Binding votes: [positive, neutral and negative counts; voters]
+Non-binding votes: [counts; voters]
+Vote thread: [public permalink]
+Approved candidate, if passed: [exact tag, commit and artifact location]
+
+[Next step consistent with the result]
+
+[Release manager name]
+
+## Release announcement
+
+Subject: [ANNOUNCE] Apache Roller [version] released
+
+The Apache Roller project is pleased to announce Apache Roller [version].
+
+[Concise description of the release and publicly releasable changes]
+
+Downloads: https://roller.apache.org/downloads/downloads.html
+Release notes: [public URL]
+[Upgrade guidance and coordinated advisory links, when ready for disclosure]
+
+[Release manager name], on behalf of the Apache Roller project
+
+Check the current ASF and project announcement guidance for recipients and
+formatting. Tally binding votes by PMC membership; do not count every +1 as binding.
diff --git a/skills/roller-release/references/website.md b/skills/roller-release/references/website.md
new file mode 100644
index 000000000..be8622281
--- /dev/null
+++ b/skills/roller-release/references/website.md
@@ -0,0 +1,39 @@
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+ https://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+# Release website update
+
+Use the user's chosen checkout of the Apache Roller website repository:
+<https://gitbox.apache.org/repos/asf/roller-website.git>.
+Inspect its README and `.asf.yaml` to confirm the publishing branch and build
+instructions; do not assume that a sibling checkout exists or is up to date.
+
+The JBake layout uses `sources/src/main/jbake/content/` for source pages and
+`content/` for rendered output. Find the download page and edit its source version,
+download URLs and verification guidance. Build with the repository's documented
+command (normally `mvn package` under `sources/`) and review both source and
+rendered changes before publishing.
+
+Use HTTPS and current ASF download infrastructure. Fetch signatures, checksums
+and KEYS from the official distribution site rather than an arbitrary mirror.
+Verify versioned archive links and all verification sidecars after propagation.
+A redirect response alone is not evidence that its destination archive exists.
+
+Publish the website only when the approved release artifacts are available.
+Verify the live page and links before announcement, then prune superseded
+releases within the agreed scope. Keep release-specific website defects in the
+release work record, not as permanent instructions in this reference.
diff --git a/skills/roller-release/scripts/bump-version.sh b/skills/roller-release/scripts/bump-version.sh
new file mode 100755
index 000000000..f45389822
--- /dev/null
+++ b/skills/roller-release/scripts/bump-version.sh
@@ -0,0 +1,68 @@
+#!/usr/bin/env bash
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# https://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+# Preview or update Roller module versions; never commits.
+# Usage: bump-version.sh <old> <new> [--write]
+# Requires Git and Python 3. Run from any directory in the target checkout.
+set -euo pipefail
+root=$(git rev-parse --show-toplevel) || exit 1
+python3 - "$root" "$@" <<'PY'
+import argparse
+from pathlib import Path
+import re
+import subprocess
+import sys
+
+root = Path(sys.argv[1])
+parser = argparse.ArgumentParser(description="Preview or update Roller module versions.")
+parser.add_argument("old")
+parser.add_argument("new")
+parser.add_argument("--write", action="store_true")
+args = parser.parse_args(sys.argv[2:])
+for value in (args.old, args.new):
+ if not re.fullmatch(r"[0-9]+\.[0-9]+\.[0-9]+(?:-[A-Za-z0-9.-]+)?", value):
+ parser.error("versions must be major.minor.patch with an optional suffix")
+expected = ["pom.xml", "app/pom.xml", "db-utils/pom.xml",
+ "assembly-release/pom.xml", "it-selenium/pom.xml"]
+missing = [name for name in expected if not (root / name).is_file()]
+if missing:
+ sys.exit("Missing expected files; no changes made: " + ", ".join(missing))
+# Match complete version element contents, not prefixes of other versions.
+pattern = re.compile(r"(?P<start><version>\s*)" + re.escape(args.old)
+ + r"(?P<end>\s*</version>)")
+changes = []
+for name in expected:
+ path = root / name
+ original = path.read_bytes()
+ text = original.decode("utf-8")
+ updated, count = pattern.subn(lambda m: m['start'] + args.new + m['end'], text)
+ if count:
+ changes.append((path, updated.encode("utf-8")))
+ print(f"{'update' if args.write else 'would update'} {name}: {count} version element(s)")
+if args.write:
+ for path, content in changes:
+ path.write_bytes(content)
+result = subprocess.run(["git", "grep", "-l", "-I", "-F", "--", args.old],
+ cwd=root, capture_output=True, text=True)
+if result.returncode not in (0, 1):
+ sys.exit(result.stderr)
+others = [name for name in result.stdout.splitlines() if name not in expected]
+print("Other tracked references to review manually:")
+print("\n".join(others) if others else "(none)")
+print("Review dependency version elements, release notes and packaging inputs manually.")
+print("The signing script takes runtime version/RC inputs; it is not rewritten.")
+print("Review git diff." if args.write else "Dry run; pass --write to apply.")
+PY
diff --git a/skills/roller-release/scripts/check-release.sh b/skills/roller-release/scripts/check-release.sh
new file mode 100755
index 000000000..63e8e1010
--- /dev/null
+++ b/skills/roller-release/scripts/check-release.sh
@@ -0,0 +1,205 @@
+#!/usr/bin/env bash
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# https://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+#
+# Verify a staged Roller release candidate the way a voter will.
+#
+# check-release.sh <dir> [--build]
+#
+# Checks every archive in <dir> for: a valid detached signature, a matching
+# checksum, an RSA signing key (>= 2048; warns below 4096), a
+# signature digest that is not SHA-1, and LICENSE/NOTICE inside the archive.
+# The source archive is additionally checked for stray compiled artifacts, and
+# with --build it is unpacked and built on the current JDK.
+#
+# Exit status is the number of failed checks, so it is usable in a gate.
+
+set -uo pipefail
+
+dir="${1:?usage: check-release.sh <dir> [--build]}"
+do_build=""
+[ "${2:-}" = "--build" ] && do_build=1
+
+fail=0
+pass() { printf 'ok %s\n' "$1"; }
+bad() { printf 'FAIL %s\n' "$1"; fail=$((fail + 1)); }
+warn() { printf 'warn %s\n' "$1"; }
+
+shopt -s nullglob
+archives=( "$dir"/*.tar.gz "$dir"/*.zip )
+
+if [ "${#archives[@]}" -eq 0 ]; then
+ bad "no .tar.gz or .zip archives found in $dir"
+ exit $fail
+fi
+
+# --- signatures -------------------------------------------------------------
+
+for f in "${archives[@]}"; do
+ base=$(basename "$f")
+
+ if [ ! -f "$f.asc" ]; then
+ bad "$base has no detached signature"
+ continue
+ fi
+
+ if ! gpg --verify "$f.asc" "$f" >/dev/null 2>&1; then
+ bad "$base signature does not verify (is the key imported?)"
+ continue
+ fi
+ pass "$base signature verifies"
+
+ # Which key, and does it meet policy? algo 1 = RSA, 17 = DSA.
+ keyid=$(gpg --list-packets "$f.asc" 2>/dev/null \
+ | awk -F'keyid ' '/keyid/ {print $2; exit}')
+ digest=$(gpg --list-packets "$f.asc" 2>/dev/null \
+ | awk -F'digest algo ' '/digest algo/ {split($2,a,","); print a[1]; exit}')
+
+ if [ -n "$keyid" ]; then
+ read -r algo bits <<<"$(gpg --with-colons --list-keys "$keyid" 2>/dev/null \
+ | awk -F: '/^pub:/ {print $4, $3; exit}')"
+ case "$algo" in
+ 1) if [ "${bits:-0}" -ge 4096 ]; then
+ pass "$base signed with RSA-$bits key $keyid"
+ elif [ "${bits:-0}" -ge 2048 ]; then
+ warn "$base signed with RSA-$bits key $keyid (policy prefers 4096)"
+ else
+ bad "$base signed with RSA-$bits key $keyid (policy requires >= 2048)"
+ fi ;;
+ 17) bad "$base signed with DSA key $keyid — policy says do not use DSA" ;;
+ "") warn "$base signing key $keyid not in local keyring; cannot check strength" ;;
+ *) warn "$base signed with key $keyid of unexpected algorithm $algo" ;;
+ esac
+ fi
+
+ # digest algo 2 = SHA-1.
+ if [ "${digest:-}" = "2" ]; then
+ bad "$base signature uses SHA-1 — policy says avoid further use of SHA-1"
+ elif [ -n "${digest:-}" ]; then
+ pass "$base signature digest algo $digest (not SHA-1)"
+ fi
+done
+
+# --- checksums --------------------------------------------------------------
+
+for f in "${archives[@]}"; do
+ base=$(basename "$f")
+ found=""
+ for alg in 512 256; do
+ [ -f "$f.sha$alg" ] || continue
+ found=1
+ have=$(shasum -a "$alg" "$f" | awk '{print $1}')
+
+ # shasum(1) format is what the policy asks for, and "shasum -c" is
+ # the authoritative check, so try it first.
+ if ( cd "$dir" && shasum -a "$alg" -c "$base.sha$alg" >/dev/null 2>&1 ); then
+ pass "$base sha$alg matches"
+ else
+ # Legacy "gpg --print-md" checksum formatting writes
+ # "<name>:" then uppercase hex in space-separated groups across
+ # following lines; "shasum -c" cannot read that. Normalise to bare
+ # lowercase hex so a correct digest in the wrong format is reported
+ # as a format problem rather than a mismatch.
+ #
+ # Truncate to the digest's own length. Filenames contain hex
+ # letters ("apache" starts with one), so an unbounded [0-9a-f]+
+ # runs past the digest and into the name.
+ width=$(( alg / 4 ))
+ want=$(tr -d ' \n' < "$f.sha$alg" \
+ | sed 's/^.*://' \
+ | tr 'A-Z' 'a-z' \
+ | grep -oE '[0-9a-f]+' \
+ | head -1 | cut -c1-"$width")
+
+ if [ "$want" = "$have" ]; then
+ warn "$base sha$alg digest is correct, but the file is not in"
+ warn " shasum(1) format or names a different path, so"
+ warn " 'shasum -c' fails for downloaders"
+ else
+ bad "$base sha$alg does NOT match"
+ fi
+ fi
+ done
+ [ -n "$found" ] || bad "$base has no .sha512 or .sha256"
+ [ -f "$f.md5" ] && bad "$base has a .md5 — MD5 files must not be published"
+ [ -f "$f.sha1" ] && bad "$base has a .sha1 — SHA-1 files must not be published"
+ [ -f "$f.sig" ] && bad "$base has a .sig — binary signatures must not be published"
+done
+
+# --- archive contents -------------------------------------------------------
+
+list_archive() {
+ case "$1" in
+ *.tar.gz) tar tzf "$1" 2>/dev/null ;;
+ *.zip) unzip -Z1 "$1" 2>/dev/null ;;
+ esac
+}
+
+for f in "${archives[@]}"; do
+ base=$(basename "$f")
+ names=$(list_archive "$f")
+
+ for required in LICENSE NOTICE; do
+ if printf '%s\n' "$names" | grep -qE "(^|/)$required(\.txt)?$"; then
+ pass "$base contains $required"
+ else
+ bad "$base is missing $required"
+ fi
+ done
+
+ case "$base" in
+ *source*)
+ junk=$(printf '%s\n' "$names" | grep -E '\.(class|jar|war)$' || true)
+ if [ -n "$junk" ]; then
+ n=$(printf '%s\n' "$junk" | wc -l | tr -d ' ')
+ bad "$base (source) contains $n compiled file(s):"
+ printf ' %s\n' $junk
+ echo " A source release should not ship third-party binaries."
+ echo " Review packaging and licensing before the vote."
+ else
+ pass "$base (source) has no compiled artifacts"
+ fi ;;
+ esac
+done
+
+# --- optional build ---------------------------------------------------------
+
+if [ -n "$do_build" ]; then
+ src=""
+ for candidate in "${archives[@]}"; do
+ case "$candidate" in *source*.tar.gz) src="$candidate"; break ;; esac
+ done
+ if [ -z "$src" ]; then
+ warn "no source tar.gz found; skipping build check"
+ else
+ tmp=$(mktemp -d)
+ if tar xzf "$src" -C "$tmp" \
+ && ( cd "$tmp"/*/ && mvn -q -ntp -DskipTests=true install >/dev/null 2>&1 ); then
+ pass "$(basename "$src") builds from source"
+ else
+ bad "$(basename "$src") does NOT build from source"
+ fi
+ rm -rf "$tmp"
+ fi
+fi
+
+echo
+if [ "$fail" -eq 0 ]; then
+ echo "All checks passed. Still download it yourself and look at it."
+else
+ echo "$fail check(s) failed — do not call the vote."
+fi
+exit "$fail"