> > > > > > The patches I've seen from the Hyper-V developers so far are just in > > > Hyper-V specific code, that can't really affect the stability of the > > > rest of the platform. I have questions about the value of doing > > > this on 2.4, given that 2.5 will branch in a reasonable amount of > > > time, but since they're eager to do it I'm not sure that it's worth > > > discouraging them ;-) > > > > > > > I think it does cause problems for people who want to upgrade OVS in > > production deployments as often it is not desirable to just take a > > large set of changes wholesale for a bugfix release. If there are many > > unrelated commits for feature development it makes it harder to > > identify what is actually going on. I'm also not sure that it is true > > that there are no changes to common code. > > Nithin, Alin, et al., why do you guys want this on branch-2.4 so badly? > Everything that Jesse is saying is right, and despite my initial instincts I'm > inclined to agree with him in the end. [Alin Gabriel Serdean: ] We would like to encourage users to start using OVS under Hyper-V so we can get as much feedback as possible. Making it more easy to use it straight out of the box and under a release version would help us in this matter.
Alin. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
