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.4 in two weeks from now, on Monday, Jul 15. With that, release should be on Thursday, Aug 15. Currently, on the mailing list we have a few patches and patch sets that were already discussed / reviewed to some extent, and we do also await new versions for several patches and patch sets for which changes were requested. These, of course, can be accepted. If there are some new patches that never been reviewed / not posted yet, please, propose an exception in reply to this email and it can be discussed. One potential exception I'm aware of is a non-RFC version of the local sampling patch set: https://patchwork.ozlabs.org/project/openvswitch/cover/[email protected]/ Design for this feature has been extensively discussed in the past few months and the kernel counterpart for the feature is almost ready. So, unless there are objections, it should be safe to get this during soft freeze. Of course, assuming that the kernel patches will be accepted and we'll get a non-RFC version of the patch set in a reasonable time for review. Best regards, Ilya Maximets. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
