eric/ReleaseKit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Add source publication command and runbook

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-05 19:04:55 +00:00
parent 7481dd0fd2
commit c83313b3b9
15 changed files with 295 additions and 60 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
docs/roadmap/policy.md
View File

@@ -1,6 +1,8 @@
# Adopt the policy framework
Status: Policy adoption complete. Release publication implementation is pending.
Status: Policy adoption complete. Source publication and its maintainer runbook
are implemented; no ReleaseKit release has been published. Executable delivery
remains pending.
Date: 2026-10-05
@@ -130,20 +132,21 @@ policy has separate defaults for applications and libraries.
successful-tag-push completion rules.
- [x] Select source only as ReleaseKit's initial deliverable in the release
policy. Supporting downstream cross-builds does not declare ReleaseKit binaries.
- [ ] Add `docs/release.md` alongside the first working publication command,
- [x] Add `docs/release.md` alongside the first working publication command,
documenting real prerequisites, authoritative remote, branch, validation,
publication, and failure recovery.
- [x] Account for first-release bootstrap: the initial publication command must
run from the captured candidate source with dependencies prepared separately.
The first release uses that source execution path before a released ReleaseKit
tool exists. Document and verify the actual command when it is implemented.
tool exists. The maintainer procedure documents the command and the temporary
repository integration test exercises the same CLI workflow.
- [ ] Add executable delivery declarations and target checks when corresponding
deliverables exist. Keep source completion and asynchronous delivery status
separate. This task is deferred unless executable deliverables are selected.
The publication command, its automated guards and offline candidate validation,
and the executable maintainer runbook remain product implementation work. This
adoption does not claim an available release command or perform publication.
The publication command, its automated guards, offline candidate validation,
and executable maintainer runbook are implemented. This adoption does not claim
that a ReleaseKit version has been published.
## Validation and completion
@@ -165,14 +168,14 @@ approval, and CI polling are not additional adoption or release gates.
## Adoption result
The seven policies, root agent orientation, developer reading guide, documentation
ownership, project grant, attribution, and license texts are in place. The product
proposal lives at `docs/roadmap/releasekit.md`; `ideas.md` remains a navigation
pointer. Future capabilities retain their proposed status, and facade
implementation remains pending in the product roadmap.
ownership, project grant, attribution, license texts, source publication command,
and maintainer runbook are in place. The product proposal lives at
`docs/roadmap/releasekit.md`; `ideas.md` remains a navigation pointer. Executable
delivery remains pending, and no ReleaseKit release has been published.
Verification covers local file and fragment links, per-policy source revision and
base version, removed template adoption sections, attribution scope and pinned
notice destinations, verbatim license bytes, and prose whitespace. The preserved
ADR decision and relocated proposal are checked against their pre-adoption source.
Release automation and its runbook remain pending under stage 4 as permitted by
this roadmap's completion criteria.
ReleaseKit's source publication command and runbook are implemented; executable
delivery declarations remain pending under stage 4.