15:00:47 <dmcbride> #startmeeting OPNFV Colorado Release
15:00:47 <collabot> Meeting started Tue Aug 16 15:00:47 2016 UTC.  The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:47 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:00:48 <collabot> The meeting name has been set to 'opnfv_colorado_release'
15:00:57 <dmcbride> #topic roll call
15:01:03 <dmcbride> #info David McBride
15:01:09 <frankbrockners> #infor Frank Brockners
15:01:12 <jmorgan1> #info Jack Morgan (Pharos)
15:01:22 <sofiawallin> #info Sofia Wallin
15:01:24 <dali`> #info Dan Lilliehorn (ARMBand/Enea)
15:01:31 <florind> #info Florin Dumitrascu (armband)
15:01:31 <kubi001> #info kubi
15:01:36 <GeraldK> #info Gerald Kunzmann
15:01:39 <ChrisPriceAB> #info Chris Price
15:01:51 <narindergupta> #info Narinder Gupta
15:02:41 <morgan_orange> #info Morgan Richomme (Functest)
15:04:36 <mtahhan__> #info Maryam Tahhan
15:16:26 <timirnich> #info Tim Irnich (SDN VPN)
15:18:25 <Greg_E_> #info Greg Elkinbard
15:18:56 <dmcbride> #topic release meeting next week during LinuxCon
15:19:40 <Greg_E_> Can we make the next week’s meeting shorter
15:20:00 <Greg_E_> or at least focus on release status from the subprojects first
15:20:06 <dmcbride> #info proposal is to change meeting time to one hour earlier (i.e. 7 a.m. PST), immediately following the TSC meeting
15:20:39 <Greg_E_> as long as we prioritize status of release in the first 30 minutes, I will be ok
15:20:40 <dmcbride> #info TSC and release calls will be conducted from onsite at the OPNFV hackfest
15:20:48 <Greg_E_> otherwise conflict with Fuel meeting
15:21:52 <ChrisPriceAB> +1 to moving forward and run stable with tested features.
15:22:22 <dmcbride> #topic stable branch and release participation
15:25:43 <dmcbride> #info simply moving features forward to updated environment is valid and sufficient for participation in the release
15:27:45 <jmorgan1> failing release critieria is failing release criteria no what is being tested
15:28:01 <jmorgan1> no matter what is being tested
15:28:28 <dmcbride> #info however, projects still need to be able to pass deployment and test requirements for the current release
15:35:09 <dmcbride> #topic Documentation
15:35:50 <dmcbride> #info documentation incomplete
15:36:05 <dmcbride> #info hoping to wrap up documentation by next week
15:37:22 <dmcbride> #info requirements for documentation for test projects incomplete
15:37:54 <dmcbride> #info test projects will continue to document their project using the same template and requirements as other projects
15:48:57 <dmcbride> #topic scenario status
15:49:22 <jmorgan1> David should define the release criteria
15:49:55 <jmorgan1> including which POD its run on
15:51:34 <dmcbride> #info there should be no constraint for testing on using a particular POD (e.g. LF POD)
15:53:25 <jmorgan1> if we wanted to get Pharos specification to help define release criteria, i will need DanSmithEricsson help since he has the back ground knowledge i don't have
15:53:33 <jmorgan1> in Colorado
15:54:10 <dmcbride> #info DanSmithEricsson points out that we lack standardization across Pharos PODs, which complicates the issue of using all POD resources for OPNFV testing
15:55:40 <fdegir> the POD where the testing runs is a constraint
15:56:27 <fdegir> only CI PODs are the PODs where the results should be taken in to account
15:56:54 <jmorgan1> #info Fatih mentions that test runs need to be done in a CI POD as its a release criteria requirment
15:57:00 <fdegir> (missing the context so this is just an input based on what I read above)
15:57:09 <dmcbride> #info clarification - testing must be done on CI PODs
15:57:16 <fdegir> thx
15:59:42 <jmorgan1> dmcbride: i updated the Releases Colorado Projects page for Pharos
16:00:03 <jmorgan1> dmcbride: Pharos is primarily a documentation effort in the pharos git repo
16:01:09 <jmorgan1> dmcbride: which defines Pharos labs and ends up http://artifacts.opnfv.org/pharos/docs/
16:01:48 <dmcbride> jmorgan1: thanks
16:01:59 <dmcbride> #endmeeting