Build/Product/Version/Point releases

I'd like to obtain from Bentley the meaning of the various product build numbers.

For instance MicroStation: "08"."11"."09"."459"

We know the 459 is a by Bentley definition a "Point Release" but to assist our strategy documentation, we would like a detailed description/definition for each of the other numbers. I've looked through various help files and other locations and have not found anything, but I've seen it before someplace.

Thanks in advance.

Parents
  • Generally speaking, Bentley version numbers are in the format of:

    [Major Version].[Minor Version].[Build Series].[Build Number]

    For example purposes, we will use version number 01.02.03.04, where each part of the version number is set like so in the policy:

    01 = Major Version
    02 = Minor Version
    03 = Build Series
    04 = Build Number

    The version number gets updated in the following situations:

    1. The "Build Number" is updated for incremental builds.

      01.02.03.04 -> 01.02.03.05

    2. The "Build Series" value is updated following a release. When the "Build Series" is updated, the "Build Number" is reset.

      01.02.03.04 -> 01.02.04.01

      Note that the "Build Number" is reset to "1" because "0" has a special meaning for build scheduling.

    3. The "Minor Version" value is updated for minor feature changes.

      01.02.03.04 -> 01.03.00.01

      The "Build Series" value is reset to "0", and the "Build Number" is set to "1"

    4. The "Major Version" value is updated for major feature changes.

      01.02.03.04 -> 02.00.00.01

      The "Minor Version" is reset to "0", the "Build Series" is reset to "0", and the "Build Number" is set to "1"

    There are rare exceptions to this, but the "Build Number" in almost all instances is sequential. Attempting to align Build Numbers across various products would increase the amount of time that it takes to make products available (particularly when you take into account localization builds), so that practice is avoided. Likewise, jumping over "Build Numbers" is a manual process that can not be automated and would again lengthen the time it would take to make products available.

      

Reply
  • Generally speaking, Bentley version numbers are in the format of:

    [Major Version].[Minor Version].[Build Series].[Build Number]

    For example purposes, we will use version number 01.02.03.04, where each part of the version number is set like so in the policy:

    01 = Major Version
    02 = Minor Version
    03 = Build Series
    04 = Build Number

    The version number gets updated in the following situations:

    1. The "Build Number" is updated for incremental builds.

      01.02.03.04 -> 01.02.03.05

    2. The "Build Series" value is updated following a release. When the "Build Series" is updated, the "Build Number" is reset.

      01.02.03.04 -> 01.02.04.01

      Note that the "Build Number" is reset to "1" because "0" has a special meaning for build scheduling.

    3. The "Minor Version" value is updated for minor feature changes.

      01.02.03.04 -> 01.03.00.01

      The "Build Series" value is reset to "0", and the "Build Number" is set to "1"

    4. The "Major Version" value is updated for major feature changes.

      01.02.03.04 -> 02.00.00.01

      The "Minor Version" is reset to "0", the "Build Series" is reset to "0", and the "Build Number" is set to "1"

    There are rare exceptions to this, but the "Build Number" in almost all instances is sequential. Attempting to align Build Numbers across various products would increase the amount of time that it takes to make products available (particularly when you take into account localization builds), so that practice is avoided. Likewise, jumping over "Build Numbers" is a manual process that can not be automated and would again lengthen the time it would take to make products available.

      

Children
No Data