]> git.proxmox.com Git - mirror_ovs.git/commit
release-process: Add transition period for LTS releases.
authorIlya Maximets <i.maximets@ovn.org>
Mon, 28 Sep 2020 02:34:45 +0000 (04:34 +0200)
committerIlya Maximets <i.maximets@ovn.org>
Tue, 10 Nov 2020 01:30:06 +0000 (02:30 +0100)
commit15177c4dadcc0470cf668cfbd9691d728f5f0721
tree87578d398bd62f638cd0467c824c45f7695370d3
parented8cf18733fd1f4865d8f16fa06180bf5a772ebe
release-process: Add transition period for LTS releases.

While LTS change happens, according to release-process.rst, we're
immediately dropping support for the old LTS and, according to
backporting-patches.rst could stop backporting bug fixes to branches
older than new LTS.  While this might be OK for an upstream project
(some upstream projects like QEMU doesn't support anything at all
except the last release) it doesn't sound like a user-friendly policy.

Below addition to the release process might make the process a bit
smoother in terms that we will continue support of branches a little
bit longer even after changing current LTS, i.e. providing at least a
minimal transition period (1 release frame) for users of old LTS.

Effectively, this change means that we will support branch-2.5 until
2.15 release, i.e. we will provide the last release, if any, on
branch-2.5 somewhere around Feb 2021. (I don't actually expect many
fixes there)

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