diff mbox series

[ovs-dev,v4,1/9] release-process: Use more accurate example releases.

Message ID 20230607194705.246951-2-mmichels@redhat.com
State Accepted
Headers show
Series OVN Release Policy Updates | expand

Checks

Context Check Description
ovsrobot/apply-robot success apply and check: success
ovsrobot/github-robot-_Build_and_Test success github build: passed
ovsrobot/github-robot-_ovn-kubernetes success github build: passed

Commit Message

Mark Michelson June 7, 2023, 7:46 p.m. UTC 
We don't use a four-digit major version, just the final two digits of
the year.

Signed-off-by: Mark Michelson <mmichels@redhat.com>
Acked-by: Dumitru Ceara <dceara@redhat.com>
---
 Documentation/internals/release-process.rst | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
diff mbox series

Patch

diff --git a/Documentation/internals/release-process.rst b/Documentation/internals/release-process.rst
index 848c2db84..d9aabf8d1 100644
--- a/Documentation/internals/release-process.rst
+++ b/Documentation/internals/release-process.rst
@@ -50,7 +50,7 @@  Scheduling`_ for the timing of each stage:
    Please propose and discuss exceptions on ovs-dev.
  
 2. Fork a release branch from main, named for the expected release number,
-   e.g. "branch-2019.10" for the branch that will yield OVN 2019.10.x.
+   e.g. "branch-25.09" for the branch that will yield OVN 25.09.x.
 
    Release branches are intended for testing and stabilization.  At this stage
    and in later stages, they should receive only bug fixes, not new features.
@@ -65,14 +65,14 @@  Scheduling`_ for the timing of each stage:
    and risk and discussed on ovs-dev before creating the branch.
 
 3. When committers come to rough consensus that the release is ready, they
-   release the .0 release on its branch, e.g. 2019.10.0 for branch-2019.10.  To
+   release the .0 release on its branch, e.g. 25.09.0 for branch-25.09.  To
    make the actual release, a committer pushes a signed tag named, e.g.
-   v2019.10.0, to the OVN repository, makes a release tarball available on
+   v25.09.0, to the OVN repository, makes a release tarball available on
    openvswitch.org, and posts a release announcement to ovs-announce.
 
 4. As bug fixes accumulate, or after important bugs or vulnerabilities are
-   fixed, committers may make additional releases from a branch: 2019.10.1,
-   2019.10.2, and so on.  The process is the same for these additional release
+   fixed, committers may make additional releases from a branch: 25.09.1,
+   25.09.2, and so on.  The process is the same for these additional release
    as for a .0 release.
 
 .. _long-term-support: