]> git.proxmox.com Git - mirror_ovs.git/commit
release-process: Standardize designation of new LTS releases.
authorIlya Maximets <i.maximets@ovn.org>
Mon, 28 Sep 2020 02:34:46 +0000 (04:34 +0200)
committerIlya Maximets <i.maximets@ovn.org>
Tue, 10 Nov 2020 01:30:06 +0000 (02:30 +0100)
commit8c6944f6913c0c819e495bee8a5e74c218dc72b2
tree2600043c07b76e53678906b1576cf4b3f893d77f
parent15177c4dadcc0470cf668cfbd9691d728f5f0721
release-process: Standardize designation of new LTS releases.

Standardize that we will mark a new release as LTS every two years
to avoid situation where we have a really old LTS branch that no-one
actually uses, but we have to support and provide releases for it.

This will also make release process more predictable, so users will
be able to rely on it and plan their upgrades accordingly.

As a bonus, 2 years support cycle kind of aligns with 2 years support
cycle of DPDK LTS releases.

Still keeping a window for us to discuss and avoid marking some
particular release as LTS in case of significant issues with it.

Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
Acked-by: Flavio Leitner <fbl@sysclose.org>
Acked-by: Kevin Traynor <ktraynor@redhat.com>
Documentation/internals/release-process.rst