Message ID | 20230531135839.2517727-7-mmichels@redhat.com |
---|---|
State | Changes Requested |
Headers | show |
Series | OVN Release Policy Updates | expand |
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 |
diff --git a/Documentation/internals/release-process.rst b/Documentation/internals/release-process.rst index 51e9d13da..b4387b5dd 100644 --- a/Documentation/internals/release-process.rst +++ b/Documentation/internals/release-process.rst @@ -152,6 +152,12 @@ approximate: | T + 6 | Sep 1, Mar 1, ... | Release version x.y.0 | +---------------+---------------------+--------------------------------------+ +After the .0 release is created for a given OVN version, that version will have +releases made every month until its support lifetime has concluded. If for some +reason, no changes occur to a supported OVN version during a month, then no +release will be made that month. Therefore, there is no guarantee about the +exact number of releases to be expected for any given OVN version. + Release Calendar ----------------
The OVN team has had no concrete policy regarding when releases are made for a given version. In the past, new releases have been made only when something critical has been found, meaning that most bug fixes applied to a given OVN version never end up in a release. This change proposes a monthly release per supported OVN version. Signed-off-by: Mark Michelson <mmichels@redhat.com> --- Documentation/internals/release-process.rst | 6 ++++++ 1 file changed, 6 insertions(+)