| Message ID | 20230531135839.2517727-1-mmichels@redhat.com |
|---|---|
| Headers | show |
| Series | OVN Release Policy Updates | expand |
On Wed, May 31, 2023 at 6:58 AM Mark Michelson <mmichels@redhat.com> 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. > > --- > 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. > > 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. > 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 | 72 +++++---- > 4 files changed, 147 insertions(+), 81 deletions(-) > > -- > 2.39.2 > > _______________________________________________ > dev mailing list > dev@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-dev Thanks Mark. I left 3 minor comments. For the series: Acked-by: Han Zhou <hzhou@ovn.org>
On Wed, May 31, 2023 at 3:58 PM Mark Michelson <mmichels@redhat.com> 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. > > --- > 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. > > 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. > 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 | 72 +++++---- > 4 files changed, 147 insertions(+), 81 deletions(-) > > -- > 2.39.2 > > _______________________________________________ > dev mailing list > dev@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-dev Thank you for putting this together, for the series: Reviewed-by: Frode Nordahl <frode.nordahl@canonical.com>