Release Tracks

Enclave uses Calendar Versioning, a versioning convention based on the data of any given release, instead of arbitrary numbers making it easier for users to understand at-a-glance when a given version of the Enclave agent was released.

Release tracks

The Enclave engineering team follow a release-when-ready philosophy, meaning updates are issued only after they have been thoroughly tested and deemed stable, unlike "move fast and break things" release models that aims for a stricter and more frequent release schedule. This helps us maintain a focus on reliability and balance continuous improvement with quality, prioritising stability for our users.

Enclave is released on two separate tracks: GA and RC. Each track indicates the expected readiness and reliability of the Enclave agent.

General Availability track (GA)

Builds of Enclave released on the General Availability (GA) track are considered stable and are the latest supported and tested versions available, suitable for production environments. We recommend all users deploy from the GA track unless they have a specific reason not to do so.

Release Candidate track (RC)

The Release Candidate (RC) track is for users who want early access to upcoming Enclave builds before they reach the stable General Availability (GA) track. Builds on the RC track often undergo additional refinement before promotion to GA. By using the RC track, users can preview upcoming features, fixes, and improvements in a controlled way, providing feedback and identifying any issues before upgrading.

This track is for users who prefer to test upcoming releases in their environment before upgrading to the latest General Availability (GA) version of Enclave.

To install from the RC track, visit the Release Candidate (RC) track installation page.