| Message ID | 20230531135839.2517727-4-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-_ovn-kubernetes | success | github build: passed |
| ovsrobot/github-robot-_Build_and_Test | fail | github build: failed |
On Wed, May 31, 2023 at 6:58 AM Mark Michelson <mmichels@redhat.com> wrote: > > Upcoming changes to the documentation will add documentation for > standard term support versions and will document a policy for when > releases are made for these versions. Our current use of "release" in > the documentation is interchangeable with "version" 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..fca93d5a8 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 version as "long-term support" or > +LTS for short. An LTS version has the distinction of being maintained for > +longer than a standard version. > (copy my comment from the v1): Shall we actually say "branch" instead of "version" or "release"? For my understanding LTS is for the branch, including any versions released from that branch. Thanks, Han > -LTS releases will receive bug fixes until the point that another LTS is > +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 > 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 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 > 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 --git a/Documentation/internals/release-process.rst b/Documentation/internals/release-process.rst index 36ee52299..fca93d5a8 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 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 releases will receive bug fixes until the point that another LTS is +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 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 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 one year of critical bug fixes and security fixes.
Upcoming changes to the documentation will add documentation for standard term support versions and will document a policy for when releases are made for these versions. Our current use of "release" in the documentation is interchangeable with "version" 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(-)