docs(roadmap): re-baseline on v0.9.1 and account for open and in-progress work - #764
Merged
Merged
Conversation
…ress work Co-Authored-By: jason.han <hanhuijun@gmail.com>
Contributor
Author
|
I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".
|
Contributor
Author
There was a problem hiding this comment.
🔍 Devin Review: 2 flags
Not posted on this PR by your GitHub settings — view them in Devin Review. (Configure)
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 and why
docs/project/roadmap.mdwas still on thev0.8.0baseline.v0.9.0(267 PRs) andv0.9.1(139 PRs) have shipped since then, and nine more PRs have merged todevelop. This PR re-baselines the roadmap onv0.9.1(b9de3b070, #614) and goes through every track again.Header and status words. Gives the exact metadata for each tag. Lists the nine PRs merged to
developafterv0.9.1(feat(state-machines): express pseudostates and deferred events as standard metadata #639, refactor(lang): remove the defer state-body extension #694, feat(export): name the standard library elements a converted model references (#731) #746, feat(grpc): Convert takes the id form, as sysml -id does (#732) #749–fix(grpc): report the parser's warnings as the workspace does #751, chore(release): merge main (0.9.1 + Windows hotfixes) back into develop #754–fix(quantity): absorb MeasurementReferences::one as the identity of the unit product #756); those are the only items now marked landed but unreleased. Adds the in progress status for work being implemented that has no PR yet. Replaces the closed-work summaries for 0.6→0.7 and 0.7→0.8 with summaries for 0.8→0.9.0 and 0.9.0→0.9.1.Gate table. Re-measured at the tag, with the
v0.8.0figure in brackets:The suite counts come from
doc-counts -site-blockson thev0.9.1tree. A new paragraph covers the three gates that read differently atdevelop's head (rejection 311; PSSM 52/12/34/5 after refactor(lang): remove the defer state-body extension #694), and points out that the README's stdlib prose still says 105/105.Coverage table removed. Since P2 moved the suites under
tests/, coverage measured from each package's own tests understates exactly the packages those suites exercise. The text now points tomake coverage/ SonarCloud instead.Release follow-through. R2 is rewritten: the Node, Java and Rust clients now publish from the core tag (ci(release): publish the Node client to npm from the core v* tag #735, ci(release): publish the Java client to Maven Central from the core v* tag #738, ci(release): publish the Rust client to crates.io from the core v* tag #739). npm and crates.io serve 0.9.1. Maven Central's 0.9.1 artifact is not confirmed, because the registry rate-limited the check. Also adds R4's wizard (feat(msi): install through a setup wizard with a destination-folder page #350), the rehearsal (ci(release): add a no-publish release rehearsal #743) and the provenance attestation (ci(release): attest SLSA provenance over the release manifest's artifacts #606).
Track status fixes:
v0.9.0.conformance/; what remains is getting the Python client onto the shared runner.v0.9.1.v0.9.1. Rewriting an existing declaration in place is not started.fails include no runtime gap any more (fix(runtime): draw a due do step against sibling entry units #525).Open PRs and in-progress work. Each open PR against
developis named where it touches an item: feat(client/java): parity with the Python client's newer surface #762, fix(migrate): write an initial into an orthogonal region as that region's entry #763, fix(export): first a then b owns its connector ends (#760) #761, feat(mdk): rename the Cameo plugin to OpenSysML MDK and bridge it into MDK's DocGen #759, fix(view): draw a part's typed ports on the interconnection and end connectors at them #757, fix(check): conformance of an implicit subsetting (#726) #748, feat(query): report the elementId Convert writes (#733) #747 and fix(editors): align SysON plugin with real 2026.9.2 artifacts #483. Work in progress with no PR is also named: parity for the Node, Rust, Julia and MATLAB clients; the SysML v1-migrateverb; the size of the WebAssembly build.Sequencing. Rewritten. The new step 1 is client parity, then the R package, then the C client. After that come X8, D13/D8, B1/B2, M1/M2, and finally the shared C ABI.
How it was verified
v0.9.1with the pilot material fetched:go test -count=1 ./tests/corpus/... -vproduces the round-trip, training and pilot-corpora figures, andgo run -C tools ./cmd/doc-counts -site-blocksproduces the suite figures.v0.9.1and atorigin/develop.git merge-base --is-ancestor. Open PRs come from the PR listing againstdevelop.python3 scripts/check-doc-links.py(0 broken),mkdocs build --strict, andgo run -C tools ./cmd/doc-counts -check("already current").Checklist
make testandmake lintpass locally (docs-only; link check, strict site build and doc-counts check run)changes/unreleased/<slug>.<section>.md, not as an edit toCHANGELOG.md(n/a, docs only)make docs-countsrun if a gate count moved (no gate count moved)F4,K5) in the body, docs, or changelogLink to Devin session: https://nasa-jpl-demo.devinenterprise.com/sessions/eb03e4319deb4f19bce2ef7d3ab1f0ed
Open in Devin Desktop: https://nasa-jpl-demo.devinenterprise.com/desktop/session/eb03e4319deb4f19bce2ef7d3ab1f0ed?variant=devin
Requested by: @HuiJun