Terracotta Downloads

The Enterprise Edition includes all the industry-leading features of Terracotta DSO, plus:

• A warranty,

• Indemnification assurance.

• Premium QA

• Direct Phone Support

• Discounted Training & Consulting

Overview

There are 4 kinds of builds:

• Nightly

• Stable

• Final

• Patch

Builds progress via a series of promotions through each phase, from Nightly to Stable to Final. Any branch which fails at any stage except Final will start over again at Nightly and work through the process again.

Nightly Builds

Naming: branch-nightly-revxxxx where branch represents the branch (e.g. 2.3) and xxxx represents the SCS revision number (e.g. 2.3-nightly-rev1345).

If you want the most recent set of code, use the nightly builds.

Nightly builds are created for every active branch. For example, during trunk only activity, only nightlies for trunk will be available, but when a release switches to feature complete, then we would have two active branches, the trunk and the release branch (e.g. 2.3)

Nightly builds are made available via an RSS feed. The RSS feed for each version is published on the download page.

Feature Complete

Naming: branch-stable0 (e.g 2.3-stable0)

When a release branch is created from the trunk, it is deemed to be Feature Complete. The first nightly that passes all automated tests is dubbed the Feature Complete build. This special build is named stable0.

Stable Builds

Naming: branch-stablen where n represents a monotonically increasing number (1, 2, 3, etc) (e.g. 2.3-stable1)

Stable builds are produced when there are no outstanding P0 or P1 bugs reported for a nightly. After a period of time and use by the community, or as deemed appropriate, a stable build is promoted to a final. This type of build is sometimes named a "Release Candidate".

Final Builds

Naming: branch.0 (e.g. 2.3.0)

Final builds are created from stable builds after an appropriate amount of time has passed, with no P0 or P1 bugs reported.

Patches

Naming: branch.n where n is the patch level (e.g. 2.3.1)

Should an issue arise with a final build, and it is deemed appropriate to produce a patch to the final build, the fix will be added to the release branch (e.g. 2.3) and a new build will be produced (a nightly). If this nightly passes an appropriate level of testing, it will be promoted to a patch build.