2017 15:53
> To: Ulrich Kleber <ulrich.kle...@huawei.com>
> Cc: Randy Levensalor <r.levensa...@cablelabs.com>; Frank Brockners
> (fbrockne) <fbroc...@cisco.com>; David McBride <
> dmcbr...@linuxfoundation.org>; TECH-DISCUSS OPNFV <
> opnfv-tech-discuss@l
.org>;
opnfv-project-le...@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [release] E-release schedule
I think having maintenance releases makes sense. From an installer
perspective, if folks want to add a new scenario for a maintenance release then
they need to carry most of the weig
ank Brockners
> (fbrockne) <fbroc...@cisco.com>; David McBride <
> dmcbr...@linuxfoundation.org>; TECH-DISCUSS OPNFV <
> opnfv-tech-discuss@lists.opnfv.org>; opnfv-project-le...@lists.opnfv.org
> Subject: Re: [opnfv-tech-discuss] [release] E-release schedule
>
> I thin
d McBride; TECH-DISCUSS OPNFV;
opnfv-project-le...@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [release] E-release schedule
Frank, +1 on your suggestions.
David, I applaud your effort to reduce the overhead for the community.
TL;DR Today I spend > 80% of my time g
e) <fbroc...@cisco.com>; David McBride
<dmcbr...@linuxfoundation.org>; TECH-DISCUSS OPNFV
<opnfv-tech-discuss@lists.opnfv.org>; opnfv-project-le...@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [release] E-release schedule
Frank, +1 on your suggestions.
David, I applaud your ef
AM
To: David McBride <dmcbr...@linuxfoundation.org>, OPNFV Tech Discussion
<opnfv-tech-discuss@lists.opnfv.org>, "opnfv-project-le...@lists.opnfv.org"
<opnfv-project-le...@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [release] E-release schedule
David,
thanks for the sum
David,
thanks for the summary. Let’s remind ourselves, that in OPNFV we’re really
trying to meet the needs of two different audiences: (1) User/consumer of a
readily integrated NFV stack – as well as marketing operations (2)
Developer/tester of an NFV stack. Audience #1 is mostly interested in
