Skip to content

Development plans

Development plans connect the long-term roadmap to concrete GitHub issues. A plan defines the outcome, boundaries, dependencies, validation, and release gates for one release or substantial workstream.

Plans are not daily task trackers. Current progress belongs in GitHub issues and milestones.

Current plans

No post-v0.8 plan is currently active. Future substantial work requires a separately reviewed and activated plan; a v0.9 plan is not implied merely by completion of v0.8.

The completed v0.8 technical-maintenance plan and v0.8 remediation plan are preserved in the archive. R1–R9 and the post-R9 COPYING distribution correction are complete. After source finalization and independent review, issue #33 qualifies the exact frozen source commit and its artifacts before the public tag is created. v0.8.0 uses Git tag, GitHub Release, and PyPI distribution without a new pyvoro2 Zenodo software-version record.

The roadmap reserves v0.9 for functional/API stabilization and downstream readiness, followed by the stable 1.0 core; prescribed cell measures move to v1.1 and mixed separator-plus-measure work to v1.2.

The completed v0.7 forward and separator API stabilization plan is also preserved in the archive.

Plan lifecycle

  • Draft — scope and design are being reviewed, or activation mechanics remain.
  • Active — approved for implementation and linked to a milestone.
  • Completed — final release source approved, outcome recorded, and moved to the archive; external publication checks may remain in a versioned release checklist.
  • Superseded — replaced by another named plan.

See Development workflow for the complete process.

Starting a plan

  1. Copy the plan template.
  2. Use a version or descriptive workstream name.
  3. Define outcome, scope, non-goals, decisions, work packages, validation, and release acceptance criteria.
  4. Review the draft before creating the full issue set.
  5. Activate it only after explicit maintainer approval and milestone linkage.

Archive

Completed and superseded plans are kept in the plan archive. They complement the changelog by preserving intent, dependencies, decisions, and deferrals.