1 <?xml version="1.0" encoding="UTF-8"?>
2 <module xmlns="urn:ietf:params:xml:ns:yang:yin:1" xmlns:sv="urn:opendaylight:yang:extension:semantic-version"
3 name="semantic-version">
4 <yang-version value="1"></yang-version>
5 <namespace uri="urn:opendaylight:yang:extension:semantic-version"></namespace>
6 <prefix value="sv"></prefix>
13 <revision date="2016-02-02"></revision>
14 <sv:semantic-version semantic-version="0.0.1"></sv:semantic-version>
15 <extension name="semantic-version">
16 <argument name="semantic-version">
17 <yin-element value="false"></yin-element>
19 <status value="current"></status>
21 <text>The OpenConfig version number for the module. This is
22 expressed as a semantic version number of the form:
25 * x corresponds to the major version,
26 * y corresponds to a minor version,
27 * z corresponds to a patch version.
28 This version corresponds to the model file within which it is
29 defined, and does not cover the whole set of OpenConfig models.
30 Where several modules are used to build up a single block of
31 functionality, the same module version is specified across each
32 file that makes up the module.
34 A major version number of 0 indicates that this model is still
35 in development (whether within OpenConfig or with industry
36 partners), and is potentially subject to change.
38 Following a release of major version 1, all modules will
39 increment major revision number where backwards incompatible
40 changes to the model are made.
42 The minor version is changed when features are added to the
43 model that do not impact current clients use of the model.
45 The patch-level version is incremented when non-feature changes
46 (such as bugfixes or clarifications to human-readable
47 descriptions that do not impact model functionality) are made
48 that maintain backwards compatibility.
50 The version number is stored in the module meta-data.