Specification documents (files) may explicitly define a "Status", typically shown immediately after the document title. When present, the "Status" applies to the individual document only and not to the entire specification or any other documents. The following table describes what the statuses mean.
The support guarantees and allowed changes are governed by the lifecycle of the document.Lifecycle stages are defined in the Versioning and Stability document.
| Status | Explanation |
|---|---|
| No explicit "Status" | Equivalent to Development. |
| Development | Breaking changes are allowed. |
| Stable | Breaking changes are no longer allowed. See stability guarantees for details. |
| Deprecated | Changes are no longer allowed, except for editorial changes. |
The specification follows OTEP 0232 maturity level definitions.
In addition to the statuses above, documents may be marked as Feature-freeze. These documents are not currently accepting new feature requests, to allow the Technical Committee time to focus on other areas of the specification. Editorial changes are still accepted. Changes that address production issues with existing features are still accepted.
Feature freeze is separate from a lifecycle status. The lifecycle represents the support requirements for the document, feature freeze only indicates the current focus of the specification community. The feature freeze label may be applied to a document at any lifecycle stage. By definition, deprecated documents have a feature freeze in place.
Some documents have individual sections with different statuses. These documents are marked with the status Mixed at the top, for clarity.