15:05:23 #startmeeting Colorado release meeting 15:05:23 Meeting started Tue Apr 19 15:05:23 2016 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:05:23 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:05:23 The meeting name has been set to 'colorado_release_meeting' 15:05:28 #topic Roll Call 15:05:30 #info Bryan Sullivan 15:05:37 #info Frank Brockners 15:05:42 #chair frankbrockners 15:05:42 Current chairs: ChrisPriceAB frankbrockners 15:05:52 #chair bryan_att 15:05:52 Current chairs: ChrisPriceAB bryan_att frankbrockners 15:05:55 #Info Simona Coppola (Intel) 15:06:07 #info Jack Morgan 15:06:23 #info Fatih Degirmenci 15:06:30 #chair fdegir 15:06:30 Current chairs: ChrisPriceAB bryan_att fdegir frankbrockners 15:06:33 #info Tim Irnich (SDN VPN) 15:06:33 #link past scenario and release meetings: https://wiki.opnfv.org/display/SWREL/Colorado+release+planning+meeting+notes+and+presentations 15:06:37 #info Ana Cunha 15:06:56 #info Trevor Cooepr 15:07:08 #topic Scenario Inventory - updates 15:07:13 #info Morgan Richomme 15:07:45 #link https://wiki.opnfv.org/display/SWREL/Colorado+scenario+inventory+and+dependencies scenario inventory 15:08:09 #info Tim Rozet 15:08:25 please take minutes, need to step away for a few minutes 15:08:33 * ChrisPriceAB looks around wildly again... 15:09:59 #info Bryan explains that one idea for the template is to inspire more features to integrate into the same scenario 15:10:46 #info Table is to explain relationship between features and scenarios 15:13:15 #info David asks is there will be installer dependancies, bryan_att answers that there will be dependencies 15:13:23 #undo 15:13:23 Removing item from minutes: 15:13:28 #info David asks if there will be installer dependancies, bryan_att answers that there will be dependencies 15:14:04 #info David also adds that the ream is establishing ownership of scenario's 15:14:43 #info Scenario owners are key to ensure scenario's are developed and tested in a timeply manner and planned across infrastructure 15:16:02 #info Sceanrio owners play the role of coordinators for the scenario shepherding it through a release. 15:16:47 #info David asks what role scenario owners should have with regard to test? 15:20:23 #info it is proposed that scenario owners are responsible for the end to end scenario for the release. 15:20:53 #info this includes that features are tested, and taking responsibility to coordinate with feature and test projects for the scenario 15:42:42 please take a look at this page for CI and development resources 15:42:43 https://wiki.opnfv.org/display/INF/Pharos+Labs 15:43:07 you have the CI POD assignments there as well 15:43:15 (might be a bit outdated) 15:43:53 fdegir: our current model needs some discussion to adjust to a senerio model, imo 15:46:46 jmorgan1: yep, can do that 15:46:55 to the others: regarding onboarding scenarios to CI 15:47:08 please add your comments/questions/thoughts to Jira issue if you like 15:47:09 https://jira.opnfv.org/browse/RELENG-86 15:57:26 https://wiki.opnfv.org/display/SWREL/Test+Release+Criteria 15:58:19 Sorry, gotta drop 16:00:47 What Morgan mentioned is important, we have good examples of how projects can be successfully integrated. We need to share those examples and as needed have mentors that can help other projects emulate the process doctor etc followed. 16:02:07 jose_lausuch: shall we add a scenario column in the test table (there is already such table in the page initiated by bryan_att) 16:02:59 yes 16:03:10 I can add that 16:04:12 but some information is overlapping 16:04:37 beauty of the wikis... 16:05:20 BTW I think we can remove the ref to qtip and policyTest (wait for the confirmation of keith) but assuming it is not listed in the candidate project, I think it is possible to do so 16:06:25 ok 16:07:18 are we done here.. - probably yes 16:07:25 think so :) 16:07:25 let's at least close this meeting 16:07:41 #endmeeting