The current state of development in OVN has resulted in many discussions happening about how things should change. The main points of the discussions have been:
* Recent releases have been much more bare than releases made two or three years ago. * Supporting as many versions of OVN as we have is a maintenance burden. * It is not well-defined what the lifetime of non-LTS OVN versions is. * We rarely, if ever, make sub-releases of released OVN versions, so it sometimes feels like backporting bugfixes is pointless. * It is not always clear as a maintainer which branches should receive backports of fixes. This set of changes aims to address these issues, while also correcting some existing errors in the documentation. The reason for the large number of patches is to allow for easy discussion about each aspect of the change. This can allow for us to reach conclusions for certain aspects and get them integrated into the documentation while allowing for other aspects to continue to be fleshed out. Mark Michelson (9): release-process: Use more accurate example releases. release-process: Switch to two releases per year. release-policy: Change "release" to "version" in LTS section. release-process: State release policy for LTS versions. release-process: Add section for standard-term support releases. release-policy: Document when versions receive new releases. backporting-patches: Change "master" to "main". backporting-patches: Fix inaccuracies in the document. backporting-patches: Add concrete policy for where backports go. .../contributing/backporting-patches.rst | 86 +++++++++---------- Documentation/internals/release-process.rst | 72 ++++++++++------ 2 files changed, 85 insertions(+), 73 deletions(-) -- 2.39.2 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
