>
>
>
> *From:* opnfv-tech-discuss@lists.opnfv.org <
> opnfv-tech-discuss@lists.opnfv.org> *On Behalf Of *David McBride
> *Sent:* Thursday, May 9, 2019 7:12 AM
> *To:* Frank Brockners (fbrockne)
> *Cc:* TSC OPNFV ; Bin Hu ;
> TECH-DISCUSS OPNFV
> *Subject:* Re:
OPNFV mailto:opnfv-...@lists.opnfv.org>>;
Bin Hu mailto:bh5...@att.com>>; TECH-DISCUSS OPNFV
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] status of Hunter release #hunter #release
Frank,
For the past several releases, I've relied on deployme
email correctly, you say that apart from the
> scenarios, we don’t really know what we’d release, correct?
>
>
>
> Thanks, Frank
>
>
>
> *From:* David McBride
> *Sent:* Donnerstag, 9. Mai 2019 15:51
> *To:* Frank Brockners (fbrockne)
> *Cc:* TSC OPNFV ; Bin Hu
; Bin Hu ;
TECH-DISCUSS OPNFV
Subject: Re: [opnfv-tech-discuss] status of Hunter release #hunter #release
Frank,
For the past several releases, I've relied on deployment and health check
status for each scenario as reported by Jenkins. Scenario owners consider all
test results and decide
Frank,
For the past several releases, I've relied on deployment and health check
status for each scenario as reported by Jenkins. Scenario owners consider
all test results and decide whether to release and communicate that intent,
for each scenario, on the scenario status page.
If projects
David,
Thanks for the summary. To be able to form an opinion on how to vote, could you
supply the following additional information?
On the scenarios: Could you supply a pointer to the test results? E.g.
http://testresults.opnfv.org/master/functest/status-apex.html is found empty.
On the
