On Tue, Aug 01, 2017 at 07:53:18PM -0400, Russell Bryant wrote: > On Tue, Aug 1, 2017 at 6:47 PM, Ben Pfaff <[email protected]> wrote: > > Hello everyone. Last week I spent an afternoon with the OVS-DPDK folks > > at Intel in Shannon, Ireland. One of the ideas that came out of it was > > a proposal for the contributors at each company to publish, at the > > beginning of each release cycle, a list of what features and other > > contributions they were planning to target for the upcoming release. > > This sounds useful to me as a way for each of the major contributors to > > get an idea of what to expect and how to coordinate over a release > > cycle. > > > > I believe that Intel is volunteering to kick this off in the 2.9 release > > cycle for OVS. I'm going to try to get us here at VMware to write a > > list as well, and I encourage other contributors to give it a try as > > well. > > > > If this works out then I'd consider adding a item for it to > > release-process.rst in the tree. > > Sure - the more communication the better. > > My only concern is continuing to set clear expecations that the > release cycle is time based. It should be clear that the list is not > a committed roadmap, but a living document communicating intent that > is subject to change if features miss the release schedule.
Good point, I agree that we should be clear that we're sticking to a time-based release plan. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
