From 7d2a7075e6fb443e3694aeb77eb1974e0feb8c4b Mon Sep 17 00:00:00 2001 From: sepehr-safari Date: Fri, 17 Jul 2026 12:10:48 +0300 Subject: [PATCH] docs: add v0.4.0 and v0.5.0 milestones to the roadmap Sequence Open OCPP Trace interop (v0.4.0, #121 and #122) and OCPP 2.0.1 support (v0.5.0) ahead of the v1.0.0 stabilization milestone, in ROADMAP and CURRENT_STATE. --- CURRENT_STATE.md | 18 ++++++++++++------ ROADMAP.md | 32 +++++++++++++++++++++++++++++++- 2 files changed, 43 insertions(+), 7 deletions(-) diff --git a/CURRENT_STATE.md b/CURRENT_STATE.md index 890217d..0c0a21e 100644 --- a/CURRENT_STATE.md +++ b/CURRENT_STATE.md @@ -8,11 +8,13 @@ ## Active Milestone -**v1.0.0 — Stable FOSS Ecosystem (next)** +**v0.4.0 - Open OCPP Trace Interop (next)** -v0.3.1 is published to npm. The v0.3 line adds trace diffing, rich scenario -assertions, CI/anonymize/diff CLI commands, 16 detection rules, 15 scenarios, -integration examples, and contributor onboarding. +v0.3.1 is published to npm (16 detection rules, 15 scenarios, trace diffing, +rich scenario assertions, and the ci/anonymize/diff CLI commands). Next up is +interoperability with the Open OCPP Trace format: reading and writing the +shared v1.1 interchange format so DebugKit exchanges traces with other OCPP +tools, checked against the shared conformance fixtures. ## What's Done @@ -226,9 +228,13 @@ integration examples, and contributor onboarding. ## What's Next -1. **v1.0.0 — Stable FOSS Ecosystem** — API stabilization, 20+ scenarios, docs +1. **v0.4.0 - Open OCPP Trace Interop** - read and write the Open OCPP Trace + v1.1 interchange format (#121, #122), checked against the shared fixtures +2. **v0.5.0 - OCPP 2.0.1 Support** - extend the engine beyond 1.6J: message + set, device model, scenarios, and detection +3. **v1.0.0 - Stable FOSS Ecosystem** - API stabilization, 20+ scenarios, docs overhaul, contributor onboarding -2. **Future** — Active scenario runner (live endpoint testing), playground, +4. **Future** - active scenario runner (live endpoint testing), playground, YAML trace format support ## Known Blockers / Decisions Pending diff --git a/ROADMAP.md b/ROADMAP.md index 55f5a1f..a832396 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -117,10 +117,40 @@ Connect to real ecosystem workflows. Attract external engagement. --- -## v1.0.0 — Stable FOSS Ecosystem +## v0.4.0 - Open OCPP Trace Interop **Status:** Next up +Interoperate with the Open OCPP Trace format, the vendor-neutral interchange +format for OCPP traces, so DebugKit reads traces other tools produce and emits +traces they can consume. + +- Parse Open OCPP Trace v1.1 input (#121) +- Export traces to Open OCPP Trace v1.1, with a `convert` CLI command (#122) +- Conformance against the shared fixtures + +**Exit criteria:** GitHub release `v0.4.0`. + +--- + +## v0.5.0 - OCPP 2.0.1 Support + +**Status:** Planned + +Extend the analysis engine beyond OCPP 1.6J to OCPP 2.0.1. + +- 2.0.1 message set and device model +- 2.0.1 scenarios and fixtures +- Detection rules adapted for 2.0.1 + +**Exit criteria:** GitHub release `v0.5.0`. + +--- + +## v1.0.0 — Stable FOSS Ecosystem + +**Status:** Planned + Mature APIs, stable formats, contributor-ready. - API stabilization