On Mon, Jan 2, 2023 at 3:08 PM Ilya Maximets <i.maxim...@ovn.org> wrote: > > Hi. As described in Documentation/internals/release-process.rst, we are > in a "soft freeze" state: > > During the freeze, we ask committers to refrain from applying patches that > add new features unless those patches were already being publicly discussed > and reviewed before the freeze began. Bug fixes are welcome at any time. > Please propose and discuss exceptions on ovs-dev. > > We should branch for version 3.1 in two weeks from now, on Monday, Jan 16. > With that, release should be on Thursday, Feb 16. > > Best regards, Ilya Maximets. > _______________________________________________ > dev mailing list > d...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-dev
Hi Ilya, Here is a list of patches I'd like to bring to your attention: * https://patchwork.ozlabs.org/project/openvswitch/list/?series=336342 This series is new, but it provides an IDL API to avoid a problem, so it falls in between "bug fixes" and "new features". Please see if it can be included in the release. * https://patchwork.ozlabs.org/project/openvswitch/list/?series=313042 This series was posted in Aug. We have been using it downstream since then. There was feedback from Adrian and he agreed with the first patch, so hopefully at least this one can catch the release. For the second patch, Adrian mentioned about a patch came later that is related. Both patches are useful but it would be better to be aligned with each other for the counter names. Could you suggest how to proceed with it? * https://patchwork.ozlabs.org/project/openvswitch/list/?series=312997 This one was also posted in Aug. The first patch got an ACK, and the second one is still waiting for feedback. Could you comment on it, too? Thanks, Han _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
