This defines ActiveViam’s policy for the support lifecycle applicable to Atoti Server, Atoti Java API, Atoti Python API, Atoti UI, Atoti JS API, and Atoti DirectQuery.

See also: Business Solutions and Modules - End of Support (EOS) Policy

Release Versioning

In this document, software release version numbers are understood as: <major #>.<minor #>.<maintenance #>

E.g., something released as “5.4.3” is under “major version” 5, under “minor version” 5.4, and the “maintenance version” 5.4.3.

For each release of a given product, the version digits are incremented according to the following principles:

• MAJOR: major rewrite with conceptual changes
• MINOR: new functionality with some incompatible API changes
• MAINTENANCE: new functionality and bug fixes that are backward compatible

General Principles

• A given minor version is supported for 2 years following General Availability (GA) of the next minor version.
  E.g., if Atoti Python API 4.1.0 is released on 2028-03-01, the EOS for Atoti Python API 4.0 will be 2030-02-28.
• Fixes for confirmed bugs that are reported against a given supported minor version will be delivered (in accordance with the relevant commercial agreement, and if technically feasible) via a new maintenance release for that minor version. Therefore we strongly recommend that customers reproduce bugs against the latest maintenance release (of the minor version they use) before reporting them.

Refer to the respective “versions list” in each product documentation to get more specifics, per released artifact, where the GA date and End-of-Support date are documented.

E.g., refer to this page to see the GA/EOS dates of the various releases of Atoti Server & Java API.

Extended Support

A customer may contract for an “Extended Support” option, for a predefined period of time after the EOS date, for an additional fee (i.e. on top of the usual software maintenance fee).

The following table illustrates the type of support resources that a customer may benefit from, depending on the EOS and “Extended Support” considerations.

NOTE - All three cases require the customer to be current on the annual maintenance fee. And under these circumstances, the customer always gets access to the support ticket management system (Jira) and the product documentation, as well as access to the latest product releases.

For a given minor version of a given product...	Before EOS Date	After EOS Date
	Standard Support	Extended Support	No Extended Support
Consideration of Feature Requests	Yes	No	No
Resolution of Critical1 Bugs	Yes	Yes2	No
Resolution of Non-Critical Bugs	Yes	No	No

<sup>1. ‘Critical’ here is defined as per commercial agreement but typically means: an error causing serious disruption, degradation or failure of the Software.
2. IF resolution is technically feasible in the minor version run by the customer.</sup>