16:00:28 #startmeeting Colorado 3.0 daily 16:00:28 Meeting started Mon Dec 5 16:00:28 2016 UTC. The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:28 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:00:28 The meeting name has been set to 'colorado_3_0_daily' 16:00:38 #topic roll call 16:00:43 #info David McBride 16:00:49 #info Fedor Zhadaev 16:01:22 #info Dan Lilliehorn (Eena/ARMBand) 16:01:47 Fedor - you're missing the snow in New Hampshire 16:01:56 #info Frank Brockners 16:02:12 #info Aric Gardner 16:02:24 #info Tim Rozet 16:02:56 Hi dmcbride, yeah, but here, in Saratov we have snow too )) 16:03:07 fzhadaev: no doubt! 16:03:24 :) 16:03:35 #topic tagging and doc links 16:04:01 aricg: please give us an overview of where we stand with project tagging and documentation links 16:04:52 I've got artifacts for armband and fuel, both are tagged 16:05:40 in one hour I will tag everyone else 16:05:40 aricg: how about Apex and Compass? 16:06:08 no word 16:06:36 apex is tagged tho 16:06:46 so I can grab the correct artifact 16:07:01 same with compass 16:08:05 as for documentation, it needs to be generated after all the tags are in place. so it should be in place later today 16:08:16 trozet: Didn't you plan to tag APEX later today? 16:08:31 frankbrockners: already tagged it 16:08:45 aricg: i updated tag and docs, I'm building hte release artifact now 16:08:52 trozet: perfect 16:09:02 trozet: is the "carbon" typo resolved in that one? 16:09:06 aricg: https://build.opnfv.org/ci/job/apex-build-colorado/103/console 16:09:10 frankbrockners: yeah 16:09:15 trozet: thanks 16:10:18 #info tags in place for Apex, Fuel, and Compass 16:10:40 #info artifacts available for Fuel and Armband 16:10:57 #info artifacts will be available for Apex and Compass later today 16:11:29 apex should be done within the next hour or so 16:12:53 #info note that joid is not releasing with Colorado 3.0 16:15:48 just chatted with Sofia and she seems satisfied with the status of documenation 16:16:48 ok - any other issues or concerns regarding Colorado 3.0? 16:17:17 We're still planning having the download site go live on Thursday (Dec 8) 16:18:18 I have a question 16:18:47 What is the list of scenarios which will release for C3.0 (i.e. for which do we have detailed test results as part of the documentation) 16:19:43 and related to that: Are there any scenarios which missed C3.0 even though they planned to participate in 3.0 (I can name os-odl_l2-fdio-ha - which deploys but we've not done sufficient testing yet) 16:20:51 frankbrockners: I can mail a list of the scenarios for C3.0 16:21:40 dmcbride: thanks - that would be good info for the TSC as well. Any input on the second question, i.e. which scenarios missed C3.0? 16:22:42 frankbrockners: I can determine that by looking at the edits to the scenario status page over the past two weeks 16:22:59 I'll send that to you, as well 16:23:23 dmcbride: thanks - please send the list to the tsc list 16:23:48 dmcbride: And another Q: Is there a link where we can review the final documentation for C3.0? 16:25:39 frankbrockners: I need to remerge all the documentation after the tags are put in, but I can send you that link after? 16:26:28 aricg: sounds good - again would be worthwhile info to share with everyone so that one can have a final review whether everything got linked properly etc. Thanks... 16:26:52 frankbrockners: I'll post it to the list 16:27:01 aricg: thanks 16:28:45 frankbrockners: part of our process is to go through and verify the links prior to the download site going live 16:29:03 that's why we wait 2 - 3 days after the release 16:44:40 #endmeeting