Refresh the roadmap - #20
Merged
Merged
Conversation
Records 0.1 and 0.2 as released with their DOIs and what actually shipped, rather than as intentions. The performance section is done, so it becomes an unreleased entry. Reorders what is next: simulation before visualisation, since a plot of an unvalidated result is a confident-looking wrong answer.
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.
The roadmap still described 0.2 as future work and listed the performance
items that shipped this week as unstarted.
actually shipped in each. The 0.2 list was written before the work and
did not match it — multi-value QCA, chart inspection, robustness sweeps
and the case typology were absent from it.
simulation lands before visualisation, because a plot of an unvalidated
result is a confident-looking wrong answer.
multi-outcome models and optional R-compatible calibration snapping are
still open, the last currently existing only as a divergence pinned by
tests.
Docs build
--strict.Summary by cubic
Refreshes the roadmap to reflect what actually shipped and what’s next. Marks 0.1 and 0.2 as released with DOIs, moves performance work to Unreleased, and reorders upcoming items by dependency.
QCAparity).Written for commit 7caedd5. Summary will update on new commits.