Skip to content

Commit 2d177ba

Browse files
committed
chore: Adding Network Operator version life-cycle
Signed-off-by: Ido Heyvi <[email protected]>
1 parent 229eb8c commit 2d177ba

File tree

1 file changed

+37
-0
lines changed

1 file changed

+37
-0
lines changed

docs/life-cycle-management.rst

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,43 @@ Life Cycle Management
2626
:local:
2727
:backlinks: none
2828

29+
===========================
30+
Network Operator Versioning
31+
===========================
32+
33+
NVIDIA Network Operator is versioned following the calendar versioning convention.
34+
35+
The version follows the pattern ``YY.MM.PP``, such as 25.1.0, 24.10.0, and 24.10.1.
36+
The first two fields, ``YY.MM`` identify a major version and indicates when the major version was initially released.
37+
The third field, ``PP``, identifies the patch version of the major version.
38+
Patch releases typically include critical bug and CVE fixes.
39+
40+
===========================
41+
Network Operator Life Cycle
42+
===========================
43+
44+
When a major version of NVIDIA Network Operator is released, the previous major version enters maintenance support
45+
and only receives patch release updates for critical bug and CVE fixes.
46+
Prior maintance release enters EOL (end-of-life) and are no longer supported and do not receive patch release updates.
47+
48+
The product life cycle and versioning are subject to change in the future.
49+
50+
.. list-table:: Support Status for Releases
51+
:header-rows: 1
52+
53+
* - Network Operator Version
54+
- Status
55+
56+
* - 25.1.x
57+
- Generally Available
58+
59+
* - 24.10.x
60+
- Maintenance
61+
62+
* - 24.7.x and lower
63+
- EOL
64+
65+
2966
=============================
3067
Ensuring Deployment Readiness
3168
=============================

0 commit comments

Comments
 (0)