Cora - 2025 Release Nomenclature

Beginning in 2025, Cora is changing the format of the release name to more accurately reflect the quarterly cadence of each release and align with the build number. Releases consist of a Release Name and a Build Number:

• Release Name: the external reference to the release notes that customers will see in marketing comms, release notes and other customer-facing communication.
• Build Number: refers to the build of the platform that is used internally for our Engineering team and for those customers who are on-prem and deploy the software directly. This number is referenced in your Cora instance under Admin > System > General > Settings.

As Cora has transitioned to a quarterly release, we are updating the numbering format. The past 2 releases of 2024 have consisted of a distinct build number that is different from the release name:

• Release 1.9.7 is referenced as Build number 1.24.3
• Release 1.9.8 is referenced as Build number 1.24.4

Closer alignment between the release name and the build number will start with the Q1 2025 release, on track to be available to our customers in early April.

New Format

The format for the release name will consist of 3 numbers in the following format:

• 25 – year of release
• 1 – quarter release where new capability will be made available
• 1 – incremental build number of the release which will increment every time we need to make a priority bug fix as part of this release.

Thus, the Q1 2025 release will be 25.1.1; the Q2 release will be 25.2.1; the Q3 release will be 25.3.1 .....etc. In 2026, the Q1 release will be 26.1.1 and so on.

The build number as found in your Admin settings will then more closely align with the common release name but provide additional information from a technical perspective.

For example, the build number in Q1 will be 1.25.1.1_X

i. 1 – Major version of the release. This will only change when a breaking change (non-reversable update) is made in the platform.

ii. 25 – Aligns with the year of the release number

iii. 1 – Aligns with the quarter of the release number

iv. 1 – An internal only number referencing the specific branch of the release

v. X – Aligns with the build version of the release number (ie. The 3rd number in the release name. This number will increase only when a priority bug fix is added to the release after it is made generally available.)

It is important to note, that similar to today, once a new quarterly release is available, it will not be deployed to a customer’s UAT or PROD site until the customer has provided approval.

This allows you to review release notes, conduct testing and schedule the release in a way that works best for you, your team and your users.

Additionally, beginning in 2025 we will look to keep our customers current and on the latest and most valuable version of product. To do this Cora will support the current version and 2 previous versions. This is to ensure customers do not fall more than 9 months behind the most recent release. This will help ensure that customers are utilizing all the new features and functionality of Cora while maintaining technical integrity in the system.