plan(v0.22): release-planning slices as requirements (release: v0.22.0)#602
Open
avrabe wants to merge 1 commit into
Open
plan(v0.22): release-planning slices as requirements (release: v0.22.0)#602avrabe wants to merge 1 commit into
avrabe wants to merge 1 commit into
Conversation
…0.22.0) v0.22 theme: complete release-planning. Files the four scoped slices as proposed requirements, each tagged release: v0.22.0 so the roadmap is live + queryable in the trace itself (`rivet list --filter '(= release "v0.22.0")'`) rather than a spreadsheet: - REQ-232 rivet list --release <ver> (#516 slice 2) - REQ-233 rivet release status <ver> burn-down (#516 slice 3, centerpiece) - REQ-234 rivet release move <id> <ver> (#516 slice 3) - REQ-235 rivet migrate --explode <source> (#490 slice 2, DD-070) Dogfood note: filing these with --set-release exercised (and confirmed) the v0.21.1 corruption fix — all four carry provenance blocks and validate cleanly. Refs: REQ-007, DD-070
📐 Rivet artifact delta
Graphgraph LR
REQ_232["REQ-232"]:::added
REQ_233["REQ-233"]:::added
REQ_234["REQ-234"]:::added
REQ_235["REQ-235"]:::added
classDef added fill:#d4edda,stroke:#28a745,color:#155724
classDef removed fill:#f8d7da,stroke:#dc3545,color:#721c24
classDef modified fill:#fff3cd,stroke:#ffc107,color:#856404
classDef overflow fill:#e2e3e5,stroke:#6c757d,color:#495057,stroke-dasharray: 3 3
Added
Posted by |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Makes the v0.22 plan live in the trace (not a spreadsheet) by filing the four scoped slices as
proposedrequirements, each taggedrelease: v0.22.0. Queryable today:v0.22 theme: complete release-planning — finish what v0.21 started (the
release:field is half-useful without a burn-down query). Each slice is small; the field + loader already exist.Dogfood notes (both are wins of the methodology):
--set-releaseexercised and confirmed the v0.21.1 corruption fix — all four carryprovenance:blocks and validate cleanly.rivet add --type requirementappended REQ-233 tocross-git-investigation.yaml(another file holding a requirement-type artifact) rather thanrequirements.yaml—find_file_for_typeis order-dependent. Functionally fine (the trace is file-agnostic), but worth a follow-up; Design: shard artifacts/requirements.yaml into per-id files so parallel adds never share a region (structural fix for #422) #490's per-id layout sidesteps it entirely.Once merged, v0.22 implementation starts at REQ-232 (
list --release).validatePASS;docs checkPASS.Refs REQ-007, DD-070.
🤖 Generated with Claude Code