Prepare the initial v0.1.0 release

This commit is contained in:
2026-10-07 02:49:47 +00:00
parent dab4fdf2b3
commit 5e60fe3113
10 changed files with 89 additions and 1198 deletions

View File

@@ -2,7 +2,7 @@
**Base Policy Version:** 1.4
**Last Updated**: 2026-10-05
**Last Updated**: 2026-10-07
**Upstream Source:** [release.md](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/release.md)
@@ -16,10 +16,10 @@ The repository-specific commands belong in `docs/release.md`. Historical release
summaries belong in `docs/releases/`. The procedure must agree with the adopted
policy and link to it rather than introduce additional release requirements.
This policy governs releases of ReleaseKit itself. Consumer release capabilities
are designed in the [product roadmap](../roadmap/releasekit.md) and acquire exact
public contracts when implemented. ReleaseKit's source publication command and
maintainer runbook are implemented; no ReleaseKit release has been published.
This policy governs releases of ReleaseKit itself. Go declarations and GoDoc
own supported consumer API contracts; the [product roadmap](../roadmap/releasekit.md)
records planned adoption and deployment work. The maintainer runbook describes
ReleaseKit's implemented source publication and hosted-page delivery procedure.
## Release Model And Completion
@@ -121,10 +121,9 @@ publish builds, verify the required build targets. Select those targets for
the project's actual support commitments; native testing on each platform
and access to particular hardware are not default release prerequisites.
The default suite and its runnable command will be established with the Go
implementation. Documentation adoption checks validate this change; they do not
create permanent release gates. ReleaseKit's source-only deliverable adds no
binary target matrix.
The publication command runs the standard offline Go test suite, followed by
any additional product checks. The [maintainer runbook](../release.md) owns its
invocation. ReleaseKit's source-only deliverable adds no binary target matrix.
Additional gates must address a concrete risk that the existing checks do not
adequately cover. Do not automatically require linting, race testing, module