Numbering Convention for Server Role Metadata Versions When Working on New Software Releases
This topic is intended for software developers who must create a new version of a server role Entity that contains a logical, predefined set of components (system software or certified third-party software) deployed in the Data Center and Site Zones that provide specific functionality for the system. metadata file to accommodate configuration changes required by a new software release. This topic explains the numbering convention you must follow when specifying version numbers in server role metadata files.
Generally, in the development process, a new code stream is created for each new update release and major release.
When creating the first version of a server role metadata file in a new code stream, you must follow a version numbering convention. This numbering convention allots 10 version numbers for a server role metadata file in each code stream.
To illustrate this numbering convention, consider the following specific example:
Assume that you are beginning work on a new 2021R1 update release and a new code stream is created for the 2021R1 rekease. There are changes to the APP server role for 2021R1. These changes require you to create a new APP server role metadata file in the new 2021R1 code stream. In this case, you would do the following:
-
Examine the latest version of the APP-metadata XML file in the 2020R1 code stream and determine the version number specified in the metadata file.
-
Specify the version number in your new server role metadata file (to exist in the new 2021R1 code stream). Specify the version number by incrementing the version number in the file to the next highest decade. As a result, a total of 10 version numbers are available for the server role metadata file in each code stream.
For example:
Assume that the version number specified for the most recent server role metadata file in the 2020R1 code stream is 15173. In this case, you must specify 15180 as the version number of the first new server role metadata file in the new 2021R1 code stream.
For each subsequent version of the server role metadata file that is created in the 2021R1 code stream (for example, to support an update release), you must increment the version number by one (15181, 15182, and so on).
When work on 2021R2 begins, a new code stream is created. For this code stream, the version number for the first new server role metadata file in the 2021R2 code stream must increment to 15190.
This numbering convention allots 10 version numbers for a server role metadata file in each code stream. This convention prevents complications from occurring when server role settings are transformed during software upgrades.