Release and Versioning Scheme for Event Broker Services

Event broker service version releases for Solace Cloud have a two-week release cadence and a two-year support cycle for LTS releases.

Solace does not use semantic versioning for our releases of Solace Software Event Brokers. In Solace Cloud, event broker services use a four-segment A.B.C.D numbering scheme that aligns to the same release and version of the underlying software event broker.

The A.B portion of the numbering scheme specifies the major release (A) and year (B) of the event broker, while the C specifies the release type and D identifies the build number for maintenance releases.

The numbering scheme of event broker services works as follows:

  • A.B identifies the major release and year of the Solace software event broker.

    For example, in version 10.25.0.123, "10" is the major release number and "25" indicates the year 2025.

  • C specifies the release type. There are three types of releases:

    • 0—Long-Term Support (LTS) release: A production-ready release available in June of each year, featuring two years of support and biweekly maintenance releases.
    • 1+—Rolling release: A generally-available release intended for new feature introduction, released every two weeks after the LTS release. For example, 10.25.2.0 is a rolling release issued four weeks after the LTS release. Rolling releases do not receive maintenance releases. Rolling releases are supported until the subsequent LTS release.For example, the Rolling release of 10.26.8 is supported until the LTS release of 10.27.0.
  • D identifies the build number of a maintenance release for the LTS releases of Solace software event broker. Maintenance releases include security fixes and product fixes. For example, 10.25.0.123 is a maintenance release of the 10.25.0 LTS release.

  • E specifies the revision of a release and version of a software event broker in Solace Cloud. E resets to zero (0) when B (the release year) changes. A value of zero for E indicates a first revision of a specific software event broker release (A.B). E increments as new maintenance and Rolling release versions are made available.

    Solace can release a specific version of a software event broker in Solace Cloud more than once to address cloud-related dependencies. For example, 10.25.0.300-123 and 10.25.0.300-145.

For more specific information about the types of Solace Cloud releases available, see Types of Releases in Solace Cloud.