14:04:23 #startmeeting OPNFV release 14:04:23 Meeting started Tue Mar 20 14:04:23 2018 UTC. The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:04:23 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:04:23 The meeting name has been set to 'opnfv_release' 14:04:29 #topic roll call 14:04:38 #info David McBride 14:04:40 #info Tim Irnich 14:04:45 #info Yifei Xue 14:04:46 #info Julien 14:04:51 #info Trevor Bramwell 14:05:28 #info Sofia Wallin 14:05:31 #info Fatih Degirmenci 14:05:54 #info Linda Wang 14:06:46 #info Tim Rozet 14:07:15 thanks for the flowers ;-) 14:07:41 #info Manuel Buil 14:10:58 #topic xci and release process 14:13:20 #info need to make a distinction between xci and CD 14:16:09 https://wiki.opnfv.org/download/attachments/8687635/XCI_Update_February2018.pdf?api=v2 14:16:26 #link https://wiki.opnfv.org/download/attachments/8687635/XCI_Update_February2018.pdf?api=v2 14:17:07 slide 4 14:17:13 ci evolution 14:23:37 slide 9 talks about how projects can populate release candidates 14:23:51 and how those candidates can be used for doing releases in cadence 14:27:05 #info project only receives OPNFV tag if it passes gates 14:27:44 #info xci would support 6-month cadence of OPNFV 14:32:15 #info Apex upstream TripleO/RDO already uses CI evolution and does promotion on a per project basis 14:45:44 trozet: that's what I was trying to explain 14:46:02 trozet: what we talk about here is what's been used by many so i don't get what the problem is 14:47:23 +1 to what Tim sys 14:47:26 says* 14:50:04 i think xci should not be a "tool" 14:50:10 openstack-ansible + bifrost is the tool 14:51:00 :) 14:51:03 thanks for that 14:51:12 we have xci 14:51:26 and we have tooling helping us to reach the level we want 14:51:35 it's like jenkins vs zuul 14:51:51 both are helping to run ci 14:58:21 there is going to be more burden on functest to support testing multiple versions of OS 15:03:50 opnfv doesn't do good job at locking versions down 15:04:07 our release is different a day after the marketing message 15:04:41 compass has package pinning itself 15:04:58 I think this should be done be installers themself 15:05:06 by 15:05:06 yifei: agree to that 15:05:12 yifei: but not all of them do that 15:05:33 not naming names 15:06:55 thanks 15:06:58 another way to solve this is having a totally offline deployment with an artifacts 17:04:32 #endmeeting