On Wed, Jun 7, 2023 at 12:47 PM Mark Michelson <[email protected]> wrote: > > 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. >
Thanks Mark. LGTM except a nit in patch-3, which can be fixed while merging. For the series: Acked-by: Han Zhou <[email protected]> > --- > V3 -> V4 differences: > * Rebased > * Added Dumitru's acks from v1 to patches 1, 4, 5, and 8. > * Updated patch 7 to have fewer scheduled point-releases based on > feedback from IRC development meetings. > > V2 -> V3 differences: > * Patch 2: Updated commit message to not mention giving longer for soft > freeze. > * Patch 3: Use "branch" instead of "version" when referring to the > development code from which releases/versions are made. > * Patch 4: Made it more explicit that LTS versions' receive bug fixes > for two years. > * Patch 9: Use "branch" instead of "version" here as well. > > V1 -> V2 differences > * Rebased > * Patch 2: Changed from one month to two week soft freeze timeframe. > * Patch 7: Updated more files to change "master" to "main". > * Patch 9: Added an example for clarification. > > V2 does not address Dumitru's questions from patch 6 about automating > minor releases. > > *** BLURB HERE *** > > Mark Michelson (9): > release-process: Use more accurate example releases. > release-process: Switch to two releases per year. > release-policy: Change "release" to "branch" 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. > Documentation: Change "master" to "main". > backporting-patches: Fix inaccuracies in the document. > backporting-patches: Add concrete policy for where backports go. > > .../internals/committer-grant-revocation.rst | 2 +- > .../internals/committer-responsibilities.rst | 8 +- > .../contributing/backporting-patches.rst | 146 ++++++++++++------ > Documentation/internals/release-process.rst | 86 +++++++---- > 4 files changed, 158 insertions(+), 84 deletions(-) > > -- > 2.39.2 > > _______________________________________________ > dev mailing list > [email protected] > https://mail.openvswitch.org/mailman/listinfo/ovs-dev _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
