13:00:19 <bh526r> #startmeeting Weekly Technical Discussion
13:00:19 <collabot> Meeting started Thu Sep  7 13:00:19 2017 UTC.  The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:19 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:00:19 <collabot> The meeting name has been set to 'weekly_technical_discussion'
13:00:40 <bh526r> #topic Roll Call
13:00:52 <morgan_orange> #info Morgan Richomme
13:00:55 <bh526r> #info Bin Hu
13:01:14 <fdegir> #info Fatih Degirmenci
13:01:35 <jmorgan1> #info Jack Morgan
13:01:40 <uli-k> #info Uli
13:01:48 * uli-k Welcome back, Jack!
13:01:54 <dmcbride> #info David McBride
13:03:46 <bh526r> #topic CD-Friendly Release Model based on XCI
13:04:02 <bh526r> #link https://wiki.opnfv.org/display/INF/Release+Process+Proposal
13:04:58 <bh526r> #info This page is subject to change. We are experimenting it by Oct 15. After Oct 15, this page will be updated based on learning
13:05:03 <bh526r> #link https://wiki.opnfv.org/pages/viewpage.action?pageId=12390152
13:05:46 <bh526r> #info We will focus on discussing this
13:10:20 <bh526r> #info Fatih introduced that Cross Community CI (XCI) aims to bring Continuous Delivery to OPNFV in order to increase the speed and agility, provide fast and tailored feedback, make it possible to shorten the time it takes for a feature/component to be part of an OPNFV scenario, ensure the composed platform always works, and get the latest and working version of platform in the hands of our users as frequently as
13:10:20 <bh526r> possible
13:11:10 <bh526r> #info Bryan indicates that this XCI model is extremely valuable for end users, and key differentiator for OPNFV
13:11:39 <bh526r> #info Then Fatih reviewed current OPNFV release model and XCI
13:12:47 <bh526r> #info And current release model makes it challenging to support CD-based development XCI
13:12:59 <bh526r> #info So a lighter model is needed
13:13:39 <bh526r> #info The proposal is that current model stays the same and renames to "stable track"
13:14:13 <bh526r> #info The new CD&XCI model is in parallel, "latest track"
13:21:08 <bh526r> #info The open question is that we may still need branch in short term (depending on the need of a project), or just patch master branch
13:21:46 <bh526r> #info David McBride indicated that based on his observation, it works well for a more mature project
13:22:24 <bh526r> #info For a brand new project, or less mature project, "stable track" works better
13:22:49 <bh526r> #info Fatih suggest that we probably let project to choose which model to work under.
13:23:36 <bh526r> #info If one model doesn't work for them, they can always change in next release
13:24:07 <bh526r> #info Bryan indicated that it is also subject to upstreams.
13:27:48 <bh526r> #info Discussion focused on whether or not carrying a patch of upstream in OPNFV
13:28:07 <bh526r> #info Dave Neary, David McBride and Bryan Sullivan gave some examples
13:35:33 <bh526r> #info Then we discussed versioning scheme. One is common version (stable track), the other is project-dependent version (latest track). Then we need a specific test framework version for XCI version which should be repeatable and reproducible on later days
13:36:04 <bh526r> #info Dave Neary shared experience from APEX project
13:41:21 <bh526r> #info Fatih clarified that tags on the diagram are for one single project
13:42:14 <bh526r> #info David McBride indicated that the critical factor is the resource.
13:59:16 <jmorgan1> +1 for more discussion
14:00:02 <bh526r> #info David McBride asked if we should continue to discuss next week, and challenge is PTG next week
14:01:37 <fdegir> #link https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-September/017756.html
14:02:23 <bh526r> #endmeeting