Version Number Scheme of Boyum Products

From January 2020, we have introduced the same product version number schema across all Boyum products. We have done this to make it easier to determine the release date of a version but also the age of already installed versions. With the change of versioning numbers, we also want to avoid unnecessary patch releases on old versions. You can apply every new version on top of previous versions, so there is no reason to keep old versions installed. If we are in the middle of a release and we need to issue an urgent bug fix, we will continue to do this as a patch for the latest available version, but we will strive to avoid this.

Version Naming

Every release carries three names. A branding name that we use to communicate about the release, a file name identifying the actual file containing the release, and a technical name embedded inside of the software that identifies the specific release and platform

Branding name

The branding name is the name we use in our publications, marketing and conversation, and it refers to a major release of a product and follows the format YYYY.MM with "For HANA" or "For MSSQL" (when applicable).

YYYY is the year of the major release and MM is the month of the major release.

Technical name

The technical name contains both the branding name and the patch version, and the format is YYYY.MM.PP.

YYYY is the year of the major release and MM is the month of the major release. PP are patches to the major release.

Example, a major release coming out in February 2020 will be called 2020.02.00. If we need to issue a maintenance release before the next major release, only the PP value is increased (+1), resulting in version 2020.02.01

A maintenance release only has bug fixes and trivial changes, no behavior modifications.

Major releases are those following our normal release schedule. That is, a product with a yearly schedule of four releases would be called: 2020.02 (for February), 2020.06 (for June), 2020.10 (for October) and 2020.12 (for December). Patches in between these months will be added as patches to existing versions. A bug fix release in May will therefore not be called 2020.05.00, but 2020.02.01 (if it is the first bugfix release after launching in February).

File Name

Our products are downloaded as zip files. The zip file name will contain more detailed information to allows easy selection of the intended version and environment.

The versioning of the file name flows this structure: <Product>_<Branding name>[_<SBO Version>][_DB Type]_<64/32 architecture>

Examples

Here are some examples to illustrate the version number scheme.

Major release version that happened in April (SBO 9.3, identical for 9.2)

Major release version that happened in June (bug fixes, no new features)

Minor release version that happened in July (bug fixes, no new features)

Major release version that happened in August (SBO 9.3, identical for 9.2)