"dev" <dev-boun...@openvswitch.org> wrote on 07/19/2016 12:58:08 PM:
> From: Ben Pfaff <b...@ovn.org> > To: dev@openvswitch.org > Cc: Ben Pfaff <b...@ovn.org> > Date: 07/19/2016 12:58 PM > Subject: [ovs-dev] [PATCH] release-process.md: Document OVS release > process and propose a schedule. > Sent by: "dev" <dev-boun...@openvswitch.org> > > This document has two different kinds of text: > > - The first sections of the document, "Release Strategy" and "Release > Numbering", describe what we've already been doing for most of the > history of Open vSwitch. If there is anything surprising in them, > then it's because our process has not been transparent enough, and not > because we're making a change. > > - The final section of the document, "Release Scheduling", is a proposal > for current and future releases. We have not had a regular release > schedule in the past, but it seems important to have one in the > future, so this section requires review and feedback from everyone in > the community. > > Signed-off-by: Ben Pfaff <b...@ovn.org> First... Acked-by: Ryan Moats <rmo...@us.ibm.com> Second... I just submitted http://patchwork.ozlabs.org/patch/651978/ to produce an ovn-controller-vtep debian package. Our architecture plans call for being able to assign TOR communication to specific nodes, so we'd like to see this or its equivalent to land as part of the 2.6.0 feature set. If it merges before the branch, great - if not, consider this an ask for inclusion before the final release. Ryan _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
