On Fri, Jul 22, 2016 at 10:26:20PM -0700, Ben Pfaff wrote: > On Sat, Jul 23, 2016 at 02:01:51AM -0300, Flavio Leitner wrote: > > On Tue, Jul 19, 2016 at 10:58:08AM -0700, Ben Pfaff wrote: > > [...] > > > +Release Scheduling > > > +------------------ > > > + > > > +Open vSwitch makes releases at the following six-month cadence, which > > > +of course is subject to change. > > > + > > > +time > > > +(months) approx dates event > > > +-------- ------------- ----------------------------------------- > > > +T Apr 1 Oct 1 release cycle for version x.y begins > > > +T + 4 Aug 1 Feb 1 branch-x.y forks from master > > > +T + 5.5 Sep 15 Mar 15 branch-x.y released as version x.y.0 > > > + > > > > I am happy to see the release cadence being documented and supported > > by the project. This will help downstream users to better support OVS. > > > > Since the above mentions that it is subject to change, I wonder if we > > could have the next release date documented somewhere (maybe a line in > > NEWS?). If anyone feels it needs more time, the developer can send a > > patch to start a discussion and if approved, it gets documented for > > everyone else's benefit. > > I think that the above *is* the documentation of the release date and, > if there's a need for a change, we can propose it here.
I read those as default tentative dates OVS would try to stick to regardless of what is happening with a particular release. Anyway, proposing here as you say works for me, ACK! :) Thanks, -- fbl _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
