> On Sep 23, 2015, at 8:33 AM, Jesse Gross <je...@nicira.com> wrote: > > On Tue, Sep 22, 2015 at 11:04 PM, Nithin Raju <nit...@vmware.com> wrote: >> hi Jesse, >> We are getting the Hyper-V solution to a state with the following goals: >> - Work “out of the box” ie. no need to make special settings such as >> disabling checksum offload, TSO, etc. >> - Reasonably stable >> >> Most of the patches we have checked in so far into 2.4 are geared towards >> these two goals. Once all of the required changes go in, and we are >> reasonably confident about the stability, we can hopefully make an >> announcement about Hyper-V support. > > This is my concern - there should not be any announcements based on > stable branches because there should be no development on stable > branches. The only thing that should go in is targeted bug fixes to > address issues that came up after the release. > > All of the goals that you listed are good things and make sense - on > the master branch. However, I don't see a need to bring these back to > 2.4. My guess is that there is no more churn in the common code on > master than with the Windows patches here. > > So please just target 2.5 as the release to make an announcement about > Hyper-V support. I promise that this release cycle won't be as long as > 2.4.
Jesse, We were hoping for a dot release off of 2.4. Like a 2.4.1 or 2.4.2 to announce support. Would that not be the right release vehicle? thanks, -- Nithin _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
