Repository navigation
epics: v1.34.0 train epic (#696) + v1.35.0 look-ahead (#697); core/look-ahead tickets tagged (PMAT-698) - #699
Merged
Merged
Conversation
…re and look-ahead tickets tagged (Refs PMAT-698) docs/roadmaps/epics.yaml defines the next tagged release, v1.34.0. Its must-carry core is PMAT-698 (bashrs 7.4.2 + the fw16 I8 fixture test), plus PMAT-604 and PMAT-652 (book v1.33.0). It also lists the merged window and the release gate. The following train, v1.35.0, is the look-ahead epic, and its kit is docs/lookahead/v1.35.0.yaml. Roadmap rows carry epic: and release: fields. Docs only, no code. Quorum receipt: docs/audits/quorum-epic-v1.34.0.md. The split passed 3/3 and its plant failed 3/3. The FR-4 admit passed 3/3 and its plant was refused 3/3. Refs #696 #697. Pmat-Ticket: PMAT-698 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
Defines the next tagged release as an epic, and the release after it as a look-ahead epic. This PR changes docs and the roadmap only; it has no code.
docs/roadmaps/epics.yamlhas two train epics:It also lists the standing theme epics (Epic: Every subcommand loads a manifest the same way #670, Epic: disk-budget never deletes what it cannot prove dead #668, Epic: manage sh-only appliances (FreeBSD / pfSense): a machine
shell:field #655, Adopt sovereign-update:updatesubcommand + daily update check (forjar) — EPIC aprender#4232 #620), the done-when commands and the release gate:release/1.34.0;docs/lookahead/v1.35.0.yamlis the look-ahead kit: criteria, carried tickets, candidates, a question and a risk.roadmap.yaml:epic: 696/release: 1.34.0;epic: 697/release: 1.35.0;must-carrylabel;The
release:v1.xlabels are left toscripts/release-goal.sh sync.Quorum receipt:
docs/audits/quorum-epic-v1.34.0.md. The split passed 3/3 and its plant (moving the v1.33.0 tag plus an unticketed core change) failed 3/3. The FR-4 over-cap admit passed 3/3 and its plant was refused 3/3.No tag is created, moved or deleted.
🤖 Generated with Claude Code