> 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.

I completely agree, the release date should not change to suit a planned 
feature. I also think the visibility of a roadmap will be beneficial when 
flagging why a planned feature will not make a release (i.e. it could be 
blocked by an external requirement such as a change required in DPDK etc.). 

For those interested an example of how this would look, below is a link to the 
recent DPDK 17.11 Intel roadmap announcement

http://dpdk.org/ml/archives/dev/2017-July/071888.html

I'm drafting a OVS 2.9 feature roadmap for Intel with OVS-DPDK  at the moment, 
should be able to send it out early next week.

Ian
 
> _______________________________________________
> dev mailing list
> [email protected]
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to