Re: [ovs-dev] [PATCH v2] release: Propose a shorter release cycle for 2.7.

On Thu, Nov 3, 2016 at 10:46 PM, Justin Pettit wrote: > > > On Nov 3, 2016, at 10:06 AM, Russell Bryant wrote: > > > > diff --git a/Documentation/release-process.md b/Documentation/release- > process.md > > index 0f8f49d..fcbd174 100644 > > ---

Re: [ovs-dev] [PATCH v2] release: Propose a shorter release cycle for 2.7.

> On Nov 3, 2016, at 10:06 AM, Russell Bryant wrote: > > diff --git a/Documentation/release-process.md > b/Documentation/release-process.md > index 0f8f49d..fcbd174 100644 > --- a/Documentation/release-process.md > +++ b/Documentation/release-process.md > @@ -88,9 +88,9 @@ of

Re: [ovs-dev] [PATCH v2] release: Propose a shorter release cycle for 2.7.

On Thu, Nov 03, 2016 at 01:06:00PM -0400, Russell Bryant wrote: > OVS recently adopted a six month release cycle. OVS doesn't > have to align to other projects, but it can be beneficial. > The dates for OVS 2.6 aligned very well to OpenStack, > which is a major consumer of OVS that usually does 6

[ovs-dev] [PATCH v2] release: Propose a shorter release cycle for 2.7.

OVS recently adopted a six month release cycle. OVS doesn't have to align to other projects, but it can be beneficial. The dates for OVS 2.6 aligned very well to OpenStack, which is a major consumer of OVS that usually does 6 month releases. OpenStack is doing a short release cycle for its Ocata