Milestone retrospectives#
Each milestone ends with a short retrospective: what was done, the deviations from the plan (each a pragmatic choice with the same intent, and why), notes for the next milestone, and the open items for the lead maintainer (PLAN Section 0.3). Scope changes and re-estimates are made here, not in the middle of a port. The M1a retrospective holds the first re-estimate of the roadmap, summarized in Plan: the short roadmap.
- Retrospective: INT1 (integration of M1b and M4)
- Retrospective: M1a (walking skeleton, CPU
sssp) - Retrospective: M1b (CUDA
sssp, CUDA core, performance harness and gates) - Retrospective: M2a (
cycle_counton the CPU backends) - Retrospective: M2b (merge of M2a,
cycle_counton CUDA) - Retrospective: M3 (framework extraction, conformance kit, 0.1 API freeze)
- Retrospective: M4 (GitHub repository and project infrastructure)
- Retrospective: M5 (the Python package, the CLI and the 0.1 documentation)
- Retrospective M6a: the CUDA plugin wheels (dyng-cu12, dyng-cu13)
- Retrospective: M6b (hardening for 0.2.0)
- Retrospective: M7 (the sssp operators engine and mosp)
- Retrospective: M8a (the ESCHER CBST store)
- Retrospective: M8b (the hypergraph container)
- Retrospective: R010 (release preparation for 0.1.0rc1)
- Retrospective: R011 (the final-release pull request for 0.1.0)
- Retrospective: R012 (the tag day of 0.1.0)
- Retrospective: R020 (release preparation for 0.2.0rc1)
- Retrospective: R021 (the final-release pull request for 0.2.0)