diff mbox series

[ovs-dev,v2,4/9] release-process: State release policy for LTS versions.

Message ID 20230531135839.2517727-5-mmichels@redhat.com
State Changes Requested
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 May 31, 2023, 1:58 p.m. UTC
The definition of "regular releases" is being kept purposely vague in
this commit because a later commit will define what the interval is for
these releases.

Signed-off-by: Mark Michelson <mmichels@redhat.com>
---
 Documentation/internals/release-process.rst | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

Comments

Han Zhou May 31, 2023, 10:58 p.m. UTC | #1
On Wed, May 31, 2023 at 6:59 AM Mark Michelson <mmichels@redhat.com> wrote:
>
> The definition of "regular releases" is being kept purposely vague in
> this commit because a later commit will define what the interval is for
> these releases.
>
> Signed-off-by: Mark Michelson <mmichels@redhat.com>
> ---
>  Documentation/internals/release-process.rst | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/internals/release-process.rst
b/Documentation/internals/release-process.rst
> index fca93d5a8..7a3b02497 100644
> --- a/Documentation/internals/release-process.rst
> +++ b/Documentation/internals/release-process.rst
> @@ -84,12 +84,13 @@ The OVN project will periodically designate a version
as "long-term support" or
>  LTS for short. An LTS version has the distinction of being maintained for
>  longer than a standard version.
>
> -LTS versions will receive bug fixes until the point that another LTS is
> -released. At that point, the old LTS will receive an additional year of
> +LTS versions will have releases made regularly until the point that
another

I think it would be more clear to say:
LTS versions will receive bug fixes and have releases made regularly
until...

"receiving bug fixes" may be implied from other parts of the document but
would just look more clear and complete here.

Thanks,
Han

> +LTS is released. At that point, the old LTS will receive an additional
year of
>  critical and security fixes. Critical fixes are those that are required
to
>  ensure basic operation (e.g. memory leak fixes, crash fixes). Security
fixes
>  are those that address concerns about exploitable flaws in OVN and that
have a
> -corresponding CVE report.
> +corresponding CVE report. Whenever such a fix is applied, a new release
will
> +be made for the LTS version.
>
>  LTS versions are scheduled to be created once every two years. This means
>  that any given LTS will receive bug fix support for two years, followed
by
> --
> 2.39.2
>
> _______________________________________________
> dev mailing list
> dev@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev
diff mbox series

Patch

diff --git a/Documentation/internals/release-process.rst b/Documentation/internals/release-process.rst
index fca93d5a8..7a3b02497 100644
--- a/Documentation/internals/release-process.rst
+++ b/Documentation/internals/release-process.rst
@@ -84,12 +84,13 @@  The OVN project will periodically designate a version as "long-term support" or
 LTS for short. An LTS version has the distinction of being maintained for
 longer than a standard version.
 
-LTS versions will receive bug fixes until the point that another LTS is
-released. At that point, the old LTS will receive an additional year of
+LTS versions will have releases made regularly until the point that another
+LTS is released. At that point, the old LTS will receive an additional year of
 critical and security fixes. Critical fixes are those that are required to
 ensure basic operation (e.g. memory leak fixes, crash fixes). Security fixes
 are those that address concerns about exploitable flaws in OVN and that have a
-corresponding CVE report.
+corresponding CVE report. Whenever such a fix is applied, a new release will
+be made for the LTS version.
 
 LTS versions are scheduled to be created once every two years. This means
 that any given LTS will receive bug fix support for two years, followed by