base-layer/commandkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Record ReleaseKit adoption completion

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-08 16:52:04 +00:00
parent 8c5fea0aae
commit c0c03285f7
2 changed files with 48 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/roadmap/releasekit.md
View File

@@ -1,6 +1,6 @@
# ReleaseKit adoption roadmap
Status: adoption selected; implementation not started.
Status: adoption complete; RK-01–RK-06 implemented and reviewed.
Date: 2026-10-08.
@@ -10,7 +10,9 @@ This roadmap defines the target state for adopting ReleaseKit as CommandKit's
maintainer release tooling and the gaps from its reviewed baseline. The
[implementation plan](implementation.md) owns ordered execution steps,
stage-specific checks, and implementation evidence. This document does not
authorize publication or claim that release tooling already exists.
authorize publication. The completed implementation and its evidence are
recorded in the
[final adoption audit](implementation.md#stage-6-audit-and-record-adoption-completion).
The [release policy](../policy/release.md),
[architecture policy](../policy/architecture.md), and
@@ -216,6 +218,14 @@ select a fresh version, prepare its note and final candidate, and follow the
runbook with publication authorization. Do not create a placeholder release
note or publish a tag merely to complete tooling adoption.
## Adoption completion
RK-01 through RK-06 were implemented and reviewed on 2026-10-08. The
[implementation plan's final audit](implementation.md#stage-6-audit-and-record-adoption-completion)
records validation results and the local commit for each completed stage. No
CommandKit release note or tag was created; preparing and publishing the first
real release remains separate authorized work under the runbook.
## Deferred capabilities
Hosted Gitea release-page delivery is deferred. If selected later, reuse the