CBORD Explains: FNS Version Numbers

This is an important announcement for Foodservice Suite®, Nutrition Service Suite®, and NetMenu® licensees.

Explaining Version Numbers
We’re changing the way we number versions of our system releases to make it easier to identify the age of the system. We are confident this will help everyone better understand and identify versions, and make it easier for you to get the support you need.

The structure of our version numbers is unchanged: Major.Minor.Branch.Build.

    OLD Example: Version 12.15.100 will be released on August 7, 2017.
    (This will be the last release using the OLD numbering scheme.)

    12 . 15 . 100 . 19520
    Major . Minor . Branch . Build

This new scheme will convey a sense of time and regularity to our versions.

    NEW Example: Version 17.8.100 will be released on September 11, 2017.
    (This will be the first release using the NEW numbering scheme.)

    17 . 8 . 100 . xxxxx
    Major . Minor . Branch . Build

    The Major version number is the 2-digit year of release: 2017.
    The Minor version number is the sequence number within the year: the 8th release of 2017.
    (The Branch and Build segments will remain unchanged.)

    The first release of 2018 will be version 18.1.100, and the second release of 2018 will be version 18.2.100, and so on.

Why the Change?
In the past, incrementing the Major version was a somewhat arbitrary decision; sometimes it was tied to support for a new DBMS; sometimes it was tied to the release of a new feature or application, or the end-of-life for an old application. We have had wild variations in the number of Minor versions per Major version.

This has resulted in some communication challenges over the years. When a customer describes a version, e.g. 10.4, it’s difficult to identify its age, both for the customer and the CBORD® Team.

Using the new numbering scheme, we’ll all be able to identify versions easily, which will help us get to solutions more quickly. In August 2019 if a customer is still using version 17.8, they are clearly in need of an upgrade since their version will be nearly two years out of date.

We release versions about every 5 weeks, so typically we will have 10 or 11 releases per year. An intelligent system of version numbers is going to improve communication and usability.

So, What Do the Version Numbers Mean?
Starting in September, version numbers will include the information we need to identify a system’s age. We hope this will help all of us better communicate going forward.