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 <mmich...@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 9a178e6b9..7c6a72a41 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 -- 2.39.2 _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
