15:02:06 #startmeeting OPNFV Colorado Release 15:02:06 Meeting started Tue Jul 5 15:02:06 2016 UTC. The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:06 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:02:06 The meeting name has been set to 'opnfv_colorado_release' 15:02:14 #topic roll call 15:02:16 #info Bryan Sullivan 15:02:24 #info Stuart Mackie 15:02:26 #info Morgan Richomme 15:02:29 #info Chris Price 15:02:32 #info Sofia Wallin 15:02:34 #chair frankbrockners 15:02:34 Current chairs: dmcbride frankbrockners 15:02:43 #info kubi 15:02:45 #chair ChrisPriceAB 15:02:45 Current chairs: ChrisPriceAB dmcbride frankbrockners 15:02:46 #info Fedor Zhadaev 15:04:51 #info Jack Morgan 15:06:11 #info Frank Brockners 15:11:09 #topic milestone status 15:11:57 #info Compass switched to Mitaka on master today 15:13:42 #info it appears that MS3 - installer/OpenStack integration has been completed 15:18:58 morgan_orange: how do I update http://testresults.opnfv.org/test/api/v1/projects/copper/cases? 15:20:00 morgan_orange: I tried to access the swagger page but it asks for a login. 15:21:44 David: job security ;-) 15:22:27 #action create wiki page for reporting on feature freeze status (David M) 15:25:41 https://wiki.opnfv.org/display/SWREL/Releases+Colorado+Projects 15:26:07 We can add columns to that page to make it easy, a y or n will suffice. 15:26:53 E.g. A new column for each milestone. I suggest avoiding wiki page proliferation. 15:28:44 Is https://wiki.opnfv.org/display/SWREL/OPNFV+C+release+planning+activities still the milestone definition plan? I don't see a 7 15:28:47 also, some of the test/code implementation depends on a stable deployment with the feature integrated in the installer to be tested on. 15:33:49 jose_lausuch: how about test project use intaller Brahmaputra release as patch gateway? 15:34:18 milestone = test implementation => 1) test run manually from a stable POD or 2) test successfully run from CI 15:35:14 #info Simona Coppola 15:35:25 chigang_: what's the point of that? we are developing test cases for Colorado :) 15:36:15 #link https://wiki.opnfv.org/display/SWREL/Colorado 15:39:51 chigang_: jose_lausuch: I think it was for developpement that are not fully tight to features included in Colorado. People could have installed a Brahmaputra version and in some cases probably tested their test suite manually towards a Brahmaputra..but now that we have beta Colorado, make more sense to use the beta version to avoid any surprise 15:40:46 #link https://wiki.opnfv.org/display/SWREL/Colorado+scenario+inventory+and+dependencies 15:42:55 I created additional columns in https://wiki.opnfv.org/display/SWREL/Releases+Colorado+Projects where projects can declare that the have met the milestones. 15:43:42 morgan_orange: agreed 15:51:08 If we are to start work on the next release, we need to branch Colorado at that point. Cherry picking for Colorado may get very complex if we have added a lot of code for D to mate in the interim. 15:53:52 I can imagine e.g, if I add tests that use Newton APIs or mod existing ones, I would rather have master focused on D at that point. 15:55:03 Someone started their meeting early? 15:55:26 i lost audio / GTM connectivity 15:55:42 everything dropped. 15:55:45 jose_lausuch: I added your topic to Infra meeting agenda for tomorrow 15:55:54 #endmeeting