Update the final candidate status - #117
Merged
Merged
Conversation
Owner
Author
|
Exact-head evidence for
This remains a candidate-status documentation change. It does not create |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Changed and Why
Update the 0.1.0 roadmap, product release specification, and release designs to
record the final candidate evidence that has now passed on remote
master.Keep the exact tagged proof and release publication open so the repository does
not claim that
v0.1.0exists before a maintainer creates it.The documented candidate evidence is for
7b65981589151f26f74eb94f29160dccce9a8140.Because this documentation PR creates a new commit, its exact head and the
resulting remote
masterwill be proved again before this batch is complete.Related Issue
Tracks #109. This PR does not close the release issue or create a tag.
Specification
docs/release-0.1.0.mddesign/release.mddesign/release-0.1.0.md, Batch 8eROADMAP.md, Batch 8The documents now distinguish completed final-candidate proof from the pending
exact-tag proof. No implementation gap is added.
Breaking Changes and Migration
None.
User-Visible Change
Verification
Exact head
be9a3e02aae7b26a86d375f817bd5cca75a3261d, Linux amd64, cold Go test cache:make external: pass, 20 external tests, 41.26 seconds. The upgrade proofbuilt its source from exact
v0.0.5without a replacement.make ci: pass, 77.50 seconds. It ran 638 default tests, 638 race tests,20 simulation tests, 19 generator tests, 45 transport tests, 50 shadow
tests, two resource-bound tests, and three fuzz targets.
go run ./internal/constraintcheck: pass.git diff --check: pass.Hosted checks for this exact PR head remain required before merge. After merge,
the resulting exact remote
masterwill receive fresh local and hosted proof.Mutation Test
N/A. Documentation-only change.
Required Checks
make cipasses locally.time.Now().time.Sleepfor synchronization.