13:00:14 <bh526r> #startmeeting Weekly Technical Discussion
13:00:14 <collabot`> Meeting started Mon Jun  3 13:00:14 2019 UTC.  The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:14 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:00:14 <collabot`> The meeting name has been set to 'weekly_technical_discussion'
13:00:41 <bh526r> #topic Roll Call
13:00:47 <bh526r> #info Bin Hu
13:00:59 <dmcbride_> #info David McBride
13:01:33 <fdegir> #info Fatih Degirmenci
13:01:51 <mbuil> #info Manuel Buil
13:02:18 <bh526r> #info Daniel Balsiger
13:02:39 <bh526r> #info Lincoln Shostak
13:02:45 <bh526r> #undo
13:02:45 <collabot`> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1d3a6d0>
13:02:58 <bh526r> #info Mark Shostak
13:03:01 <bh526r> sorry
13:03:32 <bh526r> #info Lincoln Lavoie
13:03:45 <bh526r> #info Trevor Cooper
13:03:57 <bh526r> #info Georg Kunz
13:04:16 <bh526r> #info Parker Berberian
13:04:17 <georgk> hi!
13:04:24 <bh526r> hi
13:04:36 <bh526r> #info Rabi A (Vodafone)
13:04:55 <lylavoie> #info Lincoln Lavoie (UNH-IOL)
13:05:44 <bh526r> #topic Continue to Discuss New Release Process
13:06:44 <bh526r> #info David McBride started to introduce his proposal
13:13:08 <fdegir> can we put the links to the slides to irc please?
13:13:17 <fdegir> so we can look at them in more detail offline
13:15:25 <bh526r> #info Pierre Lynch
13:17:06 <bh526r> #info Mark S asked if MS2 is t-2, and MS1 is t-5, does it make sense to move MS2 a few weeks?
13:17:38 <bh526r> #info David M said, yes, this is tentative proposal, and we can move it up a few weeks
13:29:20 <bh526r> #info Rabi indicated that specs from CNTT should be able to indicate those details
13:30:24 <bh526r> #info Manuel asked what will be specified in common references, i.e. version of ODL, or VM needs to start in 20 seconds?
13:31:07 <bh526r> #info Manuel asked if those performance criteria will be defined in release criteria.
13:31:18 <bh526r> #info David agreed
13:35:30 <bh526r> #info Mark S asked detailed explanation of project types
13:39:53 <bh526r> #info When discussing slide #11 the diagram, Bin asked 2 questions
13:44:18 <bh526r> #info (1) Installers are scenario-based projects, how will installers decouple from scenario-based projects?
13:44:41 <bh526r> (2) details of how CNTT implemented in CI?
13:44:54 <bh526r> #info (2) details of how CNTT implemented in CI?
13:50:29 <bh526r> #info Mark commented that speaking from CNTT, if CI is prescribed, and the concern is that if CNTT includes CI specs, how will it satisfy different system?
13:51:15 <bh526r> #info Bin indicated 3 different logical defects of slide #11
13:55:02 <bh526r> #info (1) From multiple installer perspective, what is the root cause of the issue that David has observed? PS the issue David described (multiple CIs because of installers in upstream) is unclear whether or not those are issues
13:55:54 <bh526r> #info (2) Without knowing the root cause, we set the goal of moving installers from upstream to downstream, it is quite prescriptive.
13:57:07 <bh526r> (3) Without knowing the answers from Bin's prior questions of (1) and (2), David agreed all those details are unknown. So without knowing the details, it is immature to propose slide #11 disgram
13:57:26 <bh526r> #info "diagram"
14:06:59 <bh526r> #info Bin suggested that CI part needs to be consolidated with long-term evolution to CircleCI
14:10:03 <bh526r> #info And decouple implementation part from CI, because of those unknown details
14:10:42 <bh526r> #info Trevor asked how those Release WG meetings were going, and whether or not projects/PTLs were engaged.
14:10:56 <bh526r> #info The attendance of release WG meetings were low
14:11:05 <bh526r> #info Trevor suggested to engage PTLs
14:11:33 <bh526r> #info Bin suggested that if we need to engage those PTLs one by one, that's the work we should do.
14:12:54 <bh526r> #info add (3) Without knowing the answers from Bin's prior questions of (1) and (2), David agreed all those details are unknown. So without knowing the details, it is immature to propose slide #11 diagram because prior was not info'ed
14:14:10 <bh526r> #info Bin suggested to have table to compare prior release MSs and new MSs for easy understanding. David agreed
14:15:54 <bh526r> #info Bin suggested that we can move forward with Iruya release planning with those improved steps (MSs). But CI related are premature as indicated above, and we should consolidated with long term CI evolution to CircleCI.
14:16:12 <bh526r> #topic AOB
14:17:01 <bh526r> #info Next week, by default, the same agenda as today. Continue discussion of new release process will be 1st agenda item, followed by new project proposals.
14:17:05 <bh526r> #endmeeting