Ataccama Lifecycle Policy
This article describes the Ataccama policy on software releases.
Release process
The release process ensures the delivery of new versions of Ataccama products. For the products available on all deployment types (Ataccama Cloud, self-managed, or hybrid), the same features are provided for each release.
Versioning
Ataccama uses semantic versioning to designate software versions in the following format: MAJOR.MINOR.PATCH.
A major version (such as v13, v14, v15) is released every 12 to 14 months.
During the first year of the product lifecycle, we continue to periodically deliver new functionalities through a number of minor versions (for example, 14.2.0, 14.3.0, and so on). We stop introducing new features to this major version once we deliver a Long-Term Support (LTS) release (see Release types for more information).
After an LTS release is available, we provide service packs or release patches containing only bug and security fixes.
Release types
Ataccama differentiates between the following release types. The type of release determines what kind of support is available for a release and for how long, which is outlined in Support period.
Long-Term Support (LTS) release
The last minor release of each major version is considered as an LTS release. These releases consist only of features introduced in previous interim releases and go through a long stabilization period to ensure the product robustness over time.
An LTS release is published every 12 to 14 months and fully supported for two years (for details, see Support period).
During the support period, we continue to maintain the software and provide bug fixes in the form of service packs and patches. However, any new features are introduced only in the subsequent major release.
Decommissioning an LTS release coincides with the release of a new major version.
Interim release
A new production-quality release is available for the ongoing major version approximately every two to three months. Interim releases are used to deliver new features and bug fixes and correspond to minor versions.
Once a major version reaches its LTS release, no new interim releases are provided.
Service packs
These releases are used to provide software maintenance during the LTS release lifecycle. They undergo the same stabilization period as interim releases in terms of functionality, upgradability, and security.
During the first year of the support period, typically every four months, a service pack is delivered to address any issues in the software. During the second year of the support period, service packs provide fixes only for critical bugs as well as any security-related issues.
Patch releases
Patch releases are provided for the currently supported versions (as described in Support period) in case of urgent security and other issues. As such, they are delivered when needed, as fast as possible, and are not part of the planned release cycle.
Each patch is also included in the following release. This applies to both interim and service packs.
For example, if the service pack 14.5.3 was patched twice (that is, there are two patch releases 14.5.3-patch1 and 14.5.3-patch2 for this version), both patches are also delivered in the next release (that is, 14.5.4), along with other less critical fixes.
Support period
At any point, Ataccama supports the two most recently published LTS versions and one latest interim release, for example, 13.9.0 (v13 LTS), 14.5.0 (v14 LTS), and 15.3.0 (v15 interim releases).
The support for the previous interim release ends one month after the following interim or LTS release is published. For instance, once 15.3.0 is published, 15.2.0 is supported for an additional month starting from that date. Likewise, 15.3.0 remains supported for a month following the release of 15.4.0.
When it comes to LTS releases, the support for the least recent LTS release ends three months after a new LTS release is published. For instance, once 15.4.0 is out, v13 LTS is supported for another three months starting from the 15.4.0 publication date.
The individual support period for your instance of Ataccama ONE might differ from this and is defined in your contract.
For additional details about what the end of the support period means, see Support ended.
Upgradability
Upgrading is available from supported versions (two most recently published LTS versions and one latest interim release) to a newly released version.
The following upgrade paths are supported depending on the release type:
- When upgrading within the same major version, it is possible to upgrade only from the previous release, regardless of the release type.
-
For example, this means you can upgrade to version 14.3.0 from version 14.2.0 but not from 14.1.0. Or, you can upgrade to version 13.9.3 from version 13.9.2 but not from 13.9.1.
- When upgrading between two major versions, it is possible to upgrade only from the latest release in the previous major version.
-
For example, you can upgrade from version 13.9.3 to version 14.3.0 but not from 13.9.1.
Supported Ataccama products
The following table shows which Ataccama products and modules are supported in which deployment mode across the released versions.
| For details about Ataccama Cloud, see Ataccama Cloud. |
| Product | Module | Self-managed | Ataccama Cloud | Custom Ataccama Cloud |
|---|---|---|---|---|
DQ&C |
All DQ&C modules not listed here |
v13.9.x, 14.5.x, 15.x |
v15.x |
v13.9x, 14.5x, 15.x |
ONE Data |
v14.5.x, 15.x |
v15.x (no hybrid mode) |
v14.5.x, 15.x (no hybrid mode) |
|
Data Stories |
No |
v15.x (no hybrid mode) |
v14.5.x, v15.x (no hybrid mode) |
|
MANTA (self-managed, v42) |
14.5.x, 15.x |
v15.x |
14.5.x, 15.x |
|
Ataccama Lineage scanners |
16.x |
16.x |
16.x |
|
DQ Firewall |
v14.5.x, 15.x |
v14.5.x, 15.x (no hybrid mode) |
v14.5.x, 15.x (no hybrid mode) |
|
Self-service hybrid Kubernetes-based DPE |
No |
v15.x |
No |
|
DQIT |
v13.9.x, 14.5.x, 15.x (upgrade only) |
No |
v13.9.x, 14.5.x, 15.x (upgrade only) |
|
Gen AI (rules, descriptions, SQL, documentation) |
No |
v15.x |
No |
|
MDM |
MDM |
v13.9.x, 14.5.x, 15.x |
No (v15.x for demos only) |
v13.9.x, 14.5.x, 15.x |
AI Matching |
No |
No (v14.5.x, 15.x for demos only) |
No |
|
RDM |
RDM |
v13.9, 14.5, 15.x (upgrade only) |
15.x (upgrade only) |
v13.9, 14.5, 15.x (upgrade only) |
Planned end of support - Ataccama components
The following table shows the planned timeline for decommissioning the Ataccama components listed.
| End of development means no new features are introduced, but the component is maintained for compatibility purposes. |
| Product | Module | Last supported version | Replacement |
|---|---|---|---|
DQ&C |
DQIT |
|
New platform capabilities (March 2025) |
RDM |
RDM |
|
New platform capabilities (March 2025) |
Planned end of support - Third-party components
The following table shows the planned timeline for ending support for the operating systems and other third-party dependencies listed.
| Platform | Component | No longer supported from | Replacement |
|---|---|---|---|
RHEL7 |
All relevant modules |
v15.x |
RHEL 9 |
CentOS 7 |
MDM, RDM |
v15.x |
RHEL 9 |
Windows 10, 11 |
MDM, RDM |
v15.x |
RHEL 9 |
PostgreSQL 13 |
All relevant modules |
v15.4 |
PostgreSQL 15 |
Support ended
The following table shows the components and releases that Ataccama no longer supports. This means the following:
-
Versions marked with an asterisk (
*) are interim releases, for which limited support is available.-
No new patches or fixes are provided for this specific version. Updates are available in the latest LTS version or service pack, or the latest interim release if no LTS release is yet available.
-
Documentation might not be available on the portal, only in PDF format.
-
-
Other versions, such as version 12, have reached the end of life and should no longer be used.
| Product | Module | End of support versions |
|---|---|---|
DQ&C |
All |
All v12 and older, 13.0.0-13.8.x*, 14.1.0-14.4.0*, 15.1.0-15.3.0* |
MDM |
MDM |
All v12 and older, 13.0.0-13.8.x*, 14.1.0-14.4.0*, 15.1.0-15.3.0* |
RDM |
RDM |
All v12 and older, 13.0.0-13.8.x*, 14.1.0-14.4.0*, 15.1.0-15.3.0* |
Was this page useful?