Repository navigation
feat: v2.8.0 — Fragmentation Go/No-Go Decision, formal close-out (#52) - #46
Merged
Merged
Conversation
…estone 52) ROADMAP.md milestone 52 already stated the final call in prose (no-go for this cycle), and every downstream consequence of that decision had already landed in earlier milestones (uart.hpp, spi.hpp, can.hpp, wire.hpp, .fusa-reqs.json all cite it as settled). This closes the milestone itself: - rcp/regmap.hpp: fix the lone stale kOptFragmentation comment that still said "go/no-go pending" to match the already-decided no-go wording used everywhere else in the tree - rcp/version.hpp / CMakeLists.txt: bump to 2.8.0 - ROADMAP.md: add the Done (v2.8.0) retrospective paragraph milestone 52 was missing, cross-referencing where the decision's consequences already live No wire-format, endpoint, or safety-mechanism behavior changes. Signed-off-by: Matt <47545907+SoundMatt@users.noreply.github.com>
Signed-off-by: Matt <47545907+SoundMatt@users.noreply.github.com> # Conflicts: # CMakeLists.txt # include/rcp/version.hpp
Signed-off-by: Matt <47545907+SoundMatt@users.noreply.github.com> # Conflicts: # CMakeLists.txt # include/rcp/version.hpp
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.
Summary
Closes ROADMAP.md milestone 52 ("Fragmentation — Go/No-Go Decision", v2.8.0). The decision itself (no-go for this cycle) and its full rationale were already written into the milestone's prose, and every downstream consequence of that decision had already landed and cross-referenced it as settled fact in earlier milestones (
rcp/uart.hpp,rcp/spi.hpp,rcp/can.hpp,rcp/wire.hpp,.fusa-reqs.json). What remained was the formal close-out:include/rcp/regmap.hpp: fix the one remaining stale comment onkOptFragmentationthat still said "go/no-go pending" — it now reads consistently with the already-decided no-go wording used everywhere else in the codebase.include/rcp/version.hpp/CMakeLists.txt: bumprcp::kVersion/ project version to2.8.0.ROADMAP.md: add the milestone's missing Done (v2.8.0): retrospective paragraph, matching the style used by milestones 44–51, cross-referencing where the decision's consequences already live in the tree.No wire-format, endpoint, or safety-mechanism behavior changes — this is a documentation and version close-out only.
Test plan
cmake --build(clang, Release) — full build succeedsctest— all 58 tests passcpp-rcp versionreports2.8.0relay conform --strictagainst the builtcpp-rcpCLI — PASS