; To: Ulrich Kleber
> Cc: Randy Levensalor ; Frank Brockners
> (fbrockne) ; 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] [releas
ich Kleber
Cc: Randy Levensalor ; Frank Brockners
(fbrockne) ; David McBride ;
TECH-DISCUSS OPNFV ;
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
br...@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 think having maintenance releases makes sense. From an installer
> perspective, if
; , "Frank Brockners
(fbrockne)" , "David McBride"
, "TECH-DISCUSS OPNFV"
, opnfv-project-le...@lists.opnfv.org
Sent: Wednesday, February 22, 2017 8:00:09 AM
Subject: Re: [opnfv-tech-discuss] [release] E-release schedule
Hi,
what Randy explains would mean that we sh
; , "Frank Brockners
(fbrockne)" , "David McBride"
, "TECH-DISCUSS OPNFV"
, opnfv-project-le...@lists.opnfv.org
Sent: Wednesday, February 22, 2017 8:00:09 AM
Subject: Re: [opnfv-tech-discuss] [release] E-release schedule
Hi,
what Randy explains would mean that we sh
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Randy
Levensalor
Sent: Friday, 17 February, 2017 00:16
To: Frank Brockners (fbrockne); David McBride; TECH-DISCUSS OPNFV;
opnfv-project-le...@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [release] E-release schedule
Frank, +1
ckne) ; David 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 getting OPNF
fv.org"
Subject: Re: [opnfv-tech-discuss] [release] E-release schedule
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 operation
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
