TetraScience Release Types

Suggest Edits

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.

To view release notes, see the following resources:

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:

Proof of Concept

A proof of concept (PoC) is a pre-release feature or component created during the initial stage of the product development lifecycle. PoCs may or may not be hidden behind a feature flag and are shared with a predetermined group of customers to make sure that the feature or component functionally works.

PoCs aren't intended for use in production environments and aren't validated for GxP use. Future versions may have breaking changes or be deprecated.

Beta Release

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 and are labeled as Beta release in the TDP release notes. Beta release Tetra Components (Tetra Integrations, Data Models, and Data Apps) aren't hidden behind a feature flag and are labeled as Beta release in either each component's release notes or artifact README file.

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. Future versions may have breaking changes or be deprecated.

Early Adopter Program

Similar to a beta release, an early adopter program (EAP) is a pre-release feature or component that is hidden behind a feature flag and shared with a select group of customers to help identify what's working along with any potential issues. However, EAP releases provide customers the option to waive any associated fees in exchange for co-marketing.

EAP features and components are not validated for GxP use and future versions may have breaking changes or be deprecated.

General Availability

A general availability (GA) release is available to the general public. All new functionalities are validated for GxP use. Deprecation notices for GA features or components are provided at least six months in advance.

Release Timing and Support

For information about release timing and support, see the following resources:

Updated about 2 months ago