15:59:35 #startmeeting Colorado 2.0 release daily 15:59:35 Meeting started Thu Nov 10 15:59:35 2016 UTC. The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:59:35 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:59:35 The meeting name has been set to 'colorado_2_0_release_daily' 15:59:49 #topic roll call 15:59:53 #info David McBride 16:00:11 #info Fedor Zhadaev 16:00:51 fzhadaev: does aricg have a pointer to Fuel artifacts for Col 2.0? 16:00:58 #info Jose Lausuch 16:01:38 dmcbride: hi. yes. I've just sent it to him 16:01:44 trozet: does aricg have a pointer to Apex artifacts for Col 2.0? 16:01:57 dmcbride: i was just pinging him to give him a pointer 16:02:06 coolio 16:03:11 fzhadaev: you indicated on Tuesday that the problem with the artifacts not being updated had been resolved 16:03:32 fzhadaev: please confirm that it's no longer an issue 16:04:17 #info Aric Gardner 16:04:20 https://build.opnfv.org/ci/view/functest/job/functest-docker-build-push-master/748/console 16:04:22 sorry 16:04:25 wrong place 16:05:24 dmcbride: no gtm? 16:05:39 fuel artifact is in place now 16:05:44 aricg: the daily is IRC-only 16:05:48 ok 16:06:16 aricg: trozet said that he was pinging you 16:06:25 aricg: emailing you 16:06:34 trozet: roger 16:06:55 aricg: have you heard from the Compass team? 16:07:28 since arm is not releasing, do we leave 1.0 on the fuel downloads page? 16:07:46 dmcbride: yes. the issue with docs if fixed. 16:07:46 *is 16:08:18 dmcbride: nothing from compass 16:08:52 and no tag in their repo 16:09:18 aricg: can we use HEAD? 16:09:18 aricg: for compass I mean 16:09:45 I see unmerged patchsets in stable/colorado 16:09:46 https://gerrit.opnfv.org/gerrit/#/q/compass 16:09:56 from this morning.. 16:11:01 at least for one of them fix version mentioned as 3.0.. 16:11:16 last merge from them in colorado is Sep 21 16:11:20 so I think we wait. 16:12:25 basically all red here: https://build.opnfv.org/ci/view/compass4nfv/ 16:15:44 Intent-to-release for Compass for 2.0 is marked 'yes' 16:16:25 looks like they dropped the ball. 16:16:30 I can't find anyone from Huawei online 16:17:14 perhaps we just soft release apex and fuel today, and wait on compass 16:17:38 3.0 is less than a month away 16:18:12 I think we need to move forward without Compass 16:18:23 they can release with 2.0 16:18:25 just leave their download page at 1.0? 16:18:30 I mean 3.0 16:18:35 yes 16:18:49 fine by me 16:18:55 I'll send an email to the TSC 16:19:16 ChrisPriceAB: any comment? 16:20:08 I am all for time based stable releases... 16:20:28 aricg: when you said "all red here" does that mean build failures? 16:20:36 yeah 16:21:58 ok - I'll be speaking with Tapio in a few minutes 16:22:19 I'll recommend to Tapio and the TSC that we proceed without Compass 16:23:24 #topic release 16:23:38 #info aricg indicates that Compass has build failures 16:23:55 #info no one online representing Compass 16:23:57 and no updates on colorado since september. 16:24:49 #info aricg also says that compass has not been updated since September 16:24:49 #info aricg also says that compass has unmerged patches 16:25:28 #info however, scenario status page indicates that compass intended to release for Col 2.0 16:25:52 #info release manager will recommend to TSC that we proceed with Colorado 2.0 release without Compass 16:26:10 any other pertinent points here? 16:26:52 ok - any other issues that anyone wants to raise? 16:27:12 aricg: you said that you have what you need for JOID? 16:28:55 no, we dont need anything for joid, they dont participate in releasing artifacts. 16:29:08 ah - right 16:29:09 and they dont tell you to check out a tag in their documentation 16:29:19 so its essentially a moot point 16:29:36 got it.. Thanks for the reminder... 16:29:41 I always forget that point 16:30:43 ok - we are out of time 16:30:48 thanks for partiipating 16:30:55 #endmeeting