About

Versioning

Public package status: the Python distributions and desktop installers are not released yet. These pages document an evolving interface, not currently usable install artifacts. View release status.

Current status

There is no supported public package version to install or pin today. Numbers used in the development source tree are internal milestones, not public releases. The Development changelog records them only to describe the interface being prepared.

Policy for the first public release

Once supported packages are published, medotter and medotter_bench will be versioned independently using Semantic Versioning: MAJOR.MINOR.PATCH.

Before 1.0:

a PATCH increment will be reserved for backwards-compatible fixes;
a MINOR increment may add surface area or include a documented breaking change;
experimental interfaces may change without a deprecation cycle.

Published installation guidance will use an exact tested version or a bounded compatible range. This page will not recommend a pin until that version is a publicly downloadable, validated artifact.

At 1.0, breaking changes to a supported interface will require a new major version.

Interface maturity before release

The labels in the current API reference describe development maturity, not a public compatibility guarantee:

Maturity	Meaning before public release
Candidate	Implemented in the development source and intended for the first supported package, but not yet publicly installable.
Experimental	Implemented for limited internal evaluation and expected to evolve.
Not supported	Registered only as a stub or roadmap item; calling it is expected to fail.

The reference still uses its existing inline stable markers to identify candidate signatures in the development source. Until a supported artifact is released, read stable as candidate, not as a package-level semver promise.

Next: Development changelog lists the internal source milestones without presenting them as public releases.