> 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 2.16 in two weeks from now, on Friday, July 16. > > Current known exception that will likely be accepted during soft-freeze, but > not prepared/reviewed yet: > - We're awaiting patches to fix performance issue in VXLAN decap offloading > implementation in userspace datapath, but this is more a bug fix than a > new feature. > Hi Ilya,
With branching for 2.16 being planned tomorrow, the other exceptions that I am aware of are as follows MFEX Optimiziation (v14 sent, awaiting ACK on minor rework) RXQ Scheduling (Acked by RH and Intel already) dpdk: Logs to announce removal of defaults for socket-mem and limit. Is there anything else on your side that you are aware that is in a position to be applied? Thanks Ian _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
