TetraScience Release Types
TetraScience regularly introduces new functionalities and enhancements in each Tetra Data Platform (TDP) and Tetra Component release.
Release Versions
Each TDP and Tetra Component version includes a three-part version number (Major.Minor.Patch). The first number shows major versions, which may include new, foundational product features. The second number shows minor versions that introduce new functionality and/or updated, backward-compatible features. The third number indicates patch versions, which include bug fixes and security updates that are made within each minor platform or component version.
Release Types
TetraScience releases new components, such as Tetra Integrations, Tetra Data Models, and Tetra Data Apps, as well as new TDP features at various degrees of maturity through the following release types.
Beta Release
| Availability | Activation | Can Be Used in Production | GxP Validation | Deprecation Notices |
|---|---|---|---|---|
| On request | Off by default | Optional | No | No |
A beta release is a pre-release feature or component that is shared with a select group of customers to help identify what's working along with any potential issues. TDP beta release features are hidden behind a feature flag, labeled as beta release in the TDP release notes, and are turned off by default. Beta release Tetra Components (Tetra Integrations, Data Models, and Data Apps), which are always optional, aren't hidden behind a feature flag. They also may or may not have release notes.
Beta releases aren't intended for use in production environments; however, customers can use a beta release feature or component in production if it works for their use case. Beta releases aren't validated for GxP use and aren't eligible for patches or upgrades after an early adopter program (EAP) or general availability (GA) version is available. Beta releases aren't guaranteed to move into a general availability (GA) release, and future versions may have breaking changes or be deprecated without a formal deprecation notice.
Early Adopter Program
| Availability | Activation | Can Be Used in Production | GxP Validation | Deprecation Notices |
|---|---|---|---|---|
| On request | Off by default | Yes | No | No |
An early adopter program (EAP) is a new or updated feature or component that TetraScience is developing in partnership with a limited set of initial customers. These customers help identify valuable improvements along with any usability issues before the feature or component is made accessible to all customers. TDP EAP features are labeled as EAP in the TDP release notes, hidden behind a feature flag, and are turned off by default. EAP Tetra Components (Tetra Integrations, Data Models, and Data Apps), which are always optional, aren't hidden behind a feature flag. They are labeled as EAP in either each component's release notes or artifact README file.
EAP features and components are not validated for GxP use. They also aren't guaranteed to move into a general availability (GA) release, and future versions may have breaking changes or be deprecated without a formal deprecation notice.
General Availability
| Availability | Activation | Can Be Used in Production | GxP Validation | Deprecation Notices |
|---|---|---|---|---|
| All customers | Available by default | Yes | Yes | Yes |
A general availability (GA) release is available to all TetraScience customers by default. All new functionalities are documented in release notes and are validated for GxP use, if applicable. Deprecation notices for GA features or components are provided at least six months in advance. Release notes are also provided.
Release Timing and Support
For information about release timing and support, see the following resources:
Release Notes
To view release notes for each TDP and Tetra Component version, see the following resources:
Updated 18 days ago