API status

Revision as of 15:00, 30 July 2013 by Tierlieb (talk | contribs) (A preview for John, who might want to weigh in on the wording)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Feature stability levels

Documentation for OX components is subject to change since the products are improved continuously. To let you know how reliable a documented feature is, we have introduced the following levels to ratethem.

In creating this we were inspired by the node.js stability index.


Deprecated

This feature is known to be problematic, and changes are planned. Do not rely on it. Use of the feature may cause warnings. Backwards compatibility should not be expected.

Changes will not be announced.

Upcoming

This feature is currently being developed and may change or be removed in future versions. Please try it out and provide feedback.

Changes will not be announced. Using the watch function to stay updated may help, but we do not guarantee to update the documentation concurrent with code changes.

New

This feature came out just recently and is in the process of settling, but has not yet had sufficient real-world testing to be considered stable.

Changes will not be announced. We recommend using the watch function for the given page to stay updated.

Stable

The API has proven satisfactory, but cleanup in the underlying code may cause minor changes. Backwards-compatibility will be maintained if reasonable.

Incompatible changes will be announced in the release notes.

Frozen

This API has been tested extensively in production and is unlikely to ever have to change. If they do occur anyway, changes will be announced in the release notes two major releases in advance.