Squirro Release Process

Squirro Release Process#

Longterm Support#

Roughly once per quarter, Squirro publishes a long-term support (LTS) release. These LTS releases undergo extended Q&A testing and are fully supported for two years. They receive security fixes and important bug fixes during the support period. As a result, LTS releases are recommended for production and UAT systems.

LTS releases have been introduced officially with Squirro 3.2.10. Until the 3.2 development series, Squirro only published the quarterly stable releases, which were thus implicitly considered LTS releases.

Intermediate Stable Versions#

In addition to the LTS releases, Squirro also releases a new intermediate stable version roughly every two weeks.

These releases are tested on a best-effort basis. They also sometimes contain intermediate versions of new features as they are still being finalized or being documented.

Thus these are great releases to keep current with Squirro’s development or to test new functionality in a development setup.

Versioning#

Squirro uses a version number scheme of X.Y.Z. Of these:

  • X is incremented rarely, and only with large system changes. The last increment was for the Python 3 migration.

  • Y is incremented after each LTS release. So X.Y.0 will be the first intermediate stable release.

  • Z is incremented with each release, whether an intermediate stable version, an LTS release, or a LTS patch. Typically the highest release number in a X.Y series will be the LTS.

Example#

  • 3.2.10 is the LTS release of the 3.3.x series.

  • 3.2.11 would be a patch LTS release if changes need to be made to 3.2.10 LTS.

  • 3.3.0 was the first intermediate stable release after the 3.2.10 LTS.

  • At some point a 3.3.x release will be declared as LTS, and the 3.4 release cycle will be started at the same time.

Contents