gamertan/sandwich-hime
1
0
Fork 0
Code Issues Pull Requests Actions Releases 4 Activity

Release Sandwich Hime v1 source and contribution policy

Browse Source 
Signed-off-by: Cole Speelman <crspeelman@gmail.com>
This commit is contained in:
gamertan
2026-09-09 09:33:44 -04:00
parent 7e89ebfaba
commit d978994b27
22 changed files with 636 additions and 104 deletions
Download Patch File Download Diff File Expand all files Collapse all files
RELEASE.md
+13 -3
View File
@@ -29,8 +29,10 @@ portability input but are not v1 release blockers or maintained promises.
Beta tags are signed, annotated, and immutable. Beta 1 is a source/module
release installed through the Go toolchain; it does not promise downloadable
prebuilt binaries. Signed binary artifacts, checksums, SBOMs, reproducible
archives, and key-recovery rehearsal are mandatory for release candidates and
final v1.
archives are mandatory for release candidates and final v1. Offline signing-key
restoration and independent second-person recovery/verification were explicitly
deferred by the maintainer for v1.0.0. Record that assurance gap in the release
review; retain the drills as follow-up work rather than claiming they passed.
### Release candidate
@@ -48,6 +50,12 @@ published assurance gap, and the documented RC observation period. A
deployment, example, classroom project, or case study in another repository is
neither imported nor required as release evidence.
For v1.0.0 the maintainer explicitly accepted the missing timed dogfooding-note
gap and deferred independent Mac installation to available alternate hardware.
Keep those dispositions visible in `ROADMAP.md`; do not recreate historical
reviews, call the install tested, or require another local profile as a
substitute. A reproduced product defect remains distinct from missing notes.
## Beta 1 publication gates (historical)
The first beta used a broader one-time platform campaign. The completed items
@@ -166,7 +174,9 @@ being mistaken for the reviewed native receipt set.
## Public source and artifacts
Gitea is the only canonical public forge. Public source is exported into a
separate, sanitized Gitea repository with fresh reviewed history. A sanitized
separate, sanitized Gitea repository with its own reviewed history. Append
reviewed publication commits to the existing public main; do not create a new
orphan history per version or push private development branches into it. A sanitized
GitHub discovery snapshot may copy reviewed public source, but it is not an
issue, contribution, release, or module origin and must never receive private
development refs or an indiscriminate Git mirror. Release binaries and