docs: ROADMAP.md — reflect actual shipped v0.1.0-v0.4.1 history - #25
Open
SoundMatt wants to merge 1 commit into
Open
docs: ROADMAP.md — reflect actual shipped v0.1.0-v0.4.1 history#25SoundMatt wants to merge 1 commit into
SoundMatt wants to merge 1 commit into
Conversation
ROADMAP.md's top labeled v0.1.0 "(current)" and listed slave-node, LDF/diagnostics, and other work as "planned" under v0.2.0/v0.3.0 — but Cargo.toml is 0.4.1, git tags confirm v0.4.0/v0.4.1 shipped, and the file's own later "Future — LIN Bus Simulator" section already correctly describes "what exists today (rust-LIN v0.4.1)" citing real, current LOC figures. Reading top-to-bottom gave two contradictory pictures of the project's status within one document. Relabel v0.1.0-v0.4.1 as shipped with their real content (cross-checked against each version's actual GitHub Release notes: v0.2.0 shipped ldf/safety/slave/seooc and go-LIN feature parity, not the old planned list's serial-port transport / break detection / schedule reloading; v0.3.0 shipped the full ISO 26262 + IEC 62443 + DO-178C artefact pack, not the old planned list's diagnostics API / NCI-NPD / no_std). Move the never-shipped planned items (SerialBus, break detection, schedule reloading, rate-limiting, diagnostics API, NCI/NPD, no_std) into a new "Planned (not yet scheduled to a specific version)" section rather than dropping them, since they're real backlog, just mislabeled under versions that ended up shipping different content. Closes #20. Signed-off-by: Matt <47545907+SoundMatt@users.noreply.github.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.
Summary
ROADMAP.mdlabeledv0.1.0as "(current)" at the top and listed slave-node/LDF/diagnostics work as "planned" under v0.2.0/v0.3.0, whileCargo.tomlis0.4.1and the file's own "Future — LIN Bus Simulator" section (further down) already correctly describes "what exists today (rust-LIN v0.4.1)". Reading top-to-bottom gave two contradictory pictures within one document.v0.1.0-v0.4.1as shipped, with their real content cross-checked against each version's actual GitHub Release notes (v0.2.0shippedldf/safety/slave/seoocand go-LIN feature parity — not the old planned list's serial-port transport/break detection/schedule reloading;v0.3.0shipped the full ISO 26262 + IEC 62443 + DO-178C artefact pack — not the old planned list's diagnostics API/NCI-NPD/no_std).Also, separately: published a retroactive GitHub Release for the
v0.4.0tag (created 2026-06-19 alongside v0.1.0-v0.3.0 but never given a published Release, leaving a gap between v0.3.0 and v0.4.1 in the Releases page) — done directly viagh release create/gh release edit --latest, not part of this diff since it's not a file change. Closes #22 as well.Closes #20, #22.
Test plan
cargo build --release --bin rust-lin --lockedcargo test --lockedgh release listconfirms v0.4.0 now has a published release and v0.4.1 remains marked Latest