On Wed, Apr 28, 2021 at 3:00 AM Dumitru Ceara <[email protected]> wrote: > > On 4/26/21 7:36 PM, Han Zhou wrote: > > On Thu, Apr 8, 2021 at 6:16 AM Dumitru Ceara <[email protected]> wrote: > >> > >> On 4/8/21 2:05 PM, Mark Michelson wrote: > >>> I pushed this to master. Thanks! > >>> > > > > Hi Dumitru, Mark, > > Hi Han, > > > Should this be backported to branches such as branch-21.03? > > We should probably bump the submodule on branch-21.03 too. One option > is indeed directly backporting the patch from master branch. > > However, we could also decide to move to the tip of latest branch-2.15 > in OVS which should include all required fixes. This has the advantage > that the stable OVN branch will use an OVS submodule version that's also > based on a stable branch. What do you think?
Thanks Dumitru! I just cherry-picked this to branch-21.03 for now, following the existing patterns. I also think it may be a good idea to use commits on a stable branch of OVS in the submodule of OVN, but not sure if it would create extra management burden. For example, what if a change in OVS is not critical enough to merge to a stable branch, but required by OVN to fix a critical issue? So I think let's not do it now until more people discuss and agree on this and make it part of our release process. > Thanks, > Dumitru > > diff --git a/ovs b/ovs > index ac09cbfcb..f2c0744d2 160000 > --- a/ovs > +++ b/ovs > @@ -1 +1 @@ > -Subproject commit ac09cbfcb70ac6f443f039d5934448bd80f74493 > +Subproject commit f2c0744d2f68c4cd2840d6e409d7b0520e4caf99 > _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
