diff mbox series

[ovs-dev,v4,3/9] release-policy: Change "release" to "branch" in LTS section.

Message ID 20230607194705.246951-4-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
Upcoming changes to the documentation will add documentation for
standard term support branches and will document a policy for when
releases are made for these branches. Our current use of "release" in
the documentation is interchangeable with "branch" but upcoming changes
will differentiate these more clearly.

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

Comments

Han Zhou June 8, 2023, 6:01 a.m. UTC | #1
On Wed, Jun 7, 2023 at 12:47 PM Mark Michelson <mmichels@redhat.com> wrote:
>
> Upcoming changes to the documentation will add documentation for
> standard term support branches and will document a policy for when
> releases are made for these branches. Our current use of "release" in
> the documentation is interchangeable with "branch" but upcoming changes
> will differentiate these more clearly.
>
> Signed-off-by: Mark Michelson <mmichels@redhat.com>
> ---
>  Documentation/internals/release-process.rst | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/internals/release-process.rst
b/Documentation/internals/release-process.rst
> index 36ee52299..e778d07aa 100644
> --- a/Documentation/internals/release-process.rst
> +++ b/Documentation/internals/release-process.rst
> @@ -77,21 +77,21 @@ Scheduling`_ for the timing of each stage:
>
>  .. _long-term-support:
>
> -Long-term Support Releases
> +Long-term Support Versions

s/Versions/Branches

With this addressed:
Acked-by: Han Zhou <hzhou@ovn.org>

>  --------------------------
>
> -The OVN project will periodically designate a release as "long-term
support" or
> -LTS for short. An LTS release has the distinction of being maintained for
> -longer than a standard release.
> +The OVN project will periodically designate a release branch as
> +"long-term support" or LTS for short. An LTS branch has the distinction
of
> +being maintained for longer than a standard branch.
>
> -LTS releases will receive bug fixes until the point that another LTS is
> +LTS branches will receive bug fixes 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.
>
> -LTS releases are scheduled to be released once every two years. This
means
> +LTS branches 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
>  one year of critical bug fixes and security fixes.
>
> --
> 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 36ee52299..e778d07aa 100644
--- a/Documentation/internals/release-process.rst
+++ b/Documentation/internals/release-process.rst
@@ -77,21 +77,21 @@  Scheduling`_ for the timing of each stage:
 
 .. _long-term-support:
 
-Long-term Support Releases
+Long-term Support Versions
 --------------------------
 
-The OVN project will periodically designate a release as "long-term support" or
-LTS for short. An LTS release has the distinction of being maintained for
-longer than a standard release.
+The OVN project will periodically designate a release branch as
+"long-term support" or LTS for short. An LTS branch has the distinction of
+being maintained for longer than a standard branch.
 
-LTS releases will receive bug fixes until the point that another LTS is
+LTS branches will receive bug fixes 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.
 
-LTS releases are scheduled to be released once every two years. This means
+LTS branches 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
 one year of critical bug fixes and security fixes.