> On Feb 25, 2015, at 9:13 PM, Ben Pfaff <b...@nicira.com> wrote: > > OVN is going to take a considerable amount of development. I don't expect > its development to break existing OVS functionality, since it's going to > take place largely in new files and directories, but it's also not going to > add anything useful to OVS until there's a lot of new code. To reduce the > amount of confusing noise in the OVS "master" branch, I propose that we > create a new branch for OVN development, called "ovn". When there's > something interesting there, we can merge it back into "master". > > Thoughts?
I think that's a great idea. > This series is what I propose to push as the initial contents of the master > branch, relative to current "master". Can I get you a review of the first patch and we push that? I've started working on ovn-controller, and it will depend on "ovn.ovsschema". I'm hoping to get support for at least "Bindings" out this week. > I suggest that patches for the "ovn" branch be posted with [PATCH ovn] in > the subject. Sounds good. --Justin _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
