14:00:10 <bh526r> #startmeeting Weekly Technical Discussion
14:00:10 <collabot`> Meeting started Thu Jan 24 14:00:10 2019 UTC.  The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:10 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:00:10 <collabot`> The meeting name has been set to 'weekly_technical_discussion'
14:00:19 <bh526r> #topic Roll Call
14:00:34 <bh526r> #info Bin Hu
14:00:41 <bh526r> #info Cristina Pauna
14:03:31 <bh526r> #info David McBride
14:05:16 <bh526r> #info Georg Kunz
14:06:55 <bh526r> #topic Strategic Discussion - Code and Release Quality
14:07:53 <bh526r> #info Cristina shared the etherpad of draft proposal of Code and Release Quality
14:08:08 <bh526r> #info Al Morton
14:08:59 <bh526r> #info The 1st is to improve project's info accuracy
14:09:51 <bh526r> #link https://etherpad.opnfv.org/p/Code_and_Release_Quality
14:12:16 <mbeierl> #info Mark Beierl
14:15:07 <bh526r> #info The identified problem is that inactive committers had negative impact on progress of projects. An example was Auto project.
14:16:05 <bh526r> #info Trevor Cooper
14:18:00 <bh526r> #info Proposal was made in etherpad
14:18:54 <bh526r> #info Bin mentioned that we can time this into release cycle
14:19:39 <bh526r> #info David mentioned that we may automate Step B as described in Etherpad
14:20:23 <bh526r> #info Al mentioned that we may set up a target date for Step A, e.g. 6 weeks to act
14:21:41 <bh526r> #info David mentioned people may not be familiar with how to add/remove committer. Cristina will provide link to wiki page and example
14:22:00 <bh526r> #info Those suggestions were captured in Etherpad
14:22:43 <bh526r> #info The 2nd is to improve Gerrit best practices
14:24:13 <bh526r> #info i.e. committer not to merge own patch
14:28:44 <bh526r> #info Suggestion about PTL exception and single committer exception
14:30:04 <bh526r> #info Suggestion to start with A wiki page to emphasize  that self-merge is discouraged, and decide if we enforce it later on. This will minimize the impact on projects that most committers are inactive.
14:30:44 <bh526r> #info Suggestions are captured in etherpad
14:31:15 <bh526r> #info The 3rd is to use FuncTest to verify installer patches
14:32:00 <bh526r> #info This is already implemented.
14:33:10 <bh526r> #info The change is to document it and make it mandatory in the future so that we won't drop this best practice.
14:35:07 <bh526r> #info David asked if it is configurable. Cristina suggested that if you want to disable it, it needs approval from Release Manager or TSC
14:35:50 <bh526r> #info Suggestion is captured in etherpad
14:36:22 <bh526r> #info The 4th is to reduce the time it takes for running the tests
14:38:33 <bh526r> #info The issue is that it takes long time to run all tests in FuncTest test suites. It takes more than 4 hours in almost all cases. On a regular basis, 10 hours even not enough (then timed out after 10 hours)
14:40:23 <bh526r> #info Possible solution includes (A) parallel testing (B) improve functest failure detection (C) daily jobs and weekly jobs
14:40:44 <bh526r> #info Expect Cedric to drive the best solution
14:41:24 <bh526r> #info David mentioned that we may run basic tests initially, and advanced tests only after passing basic tests
14:43:34 <bh526r> #info Cristina asked what is the reasonable time for running FuncTest
14:44:04 <bh526r> #info Mark asked if the cycle time is for full test or for a patch
14:44:18 <bh526r> #info Cristina clarified that it is not for a patch
14:44:38 <bh526r> #info 2.5 years ago, it took 2.5 hours to run a full cycle of functest
14:47:46 <bh526r> #info Mark mentioned that if one project is in the formal process, 2-3 hours of running functest is reasonable on daily basis.
14:51:59 <bh526r> #info David mentioned that it also intersects with Release Process discussion
14:54:57 <bh526r> #info Test WG can continue working on it, while Release WG keeps on working on process.
14:55:18 <bh526r> #info It is challenging to just say 20 minutes or 2 hours is enough
14:56:24 <bh526r> #info Cristina will send an email to mailing list, with all comments we received today, and look for more input / comments
14:58:12 <bh526r> #info The target is for TSC approval on Feb 5 (of at least some of those ideas), if discussion is going well. Understand some other ideas may need more time
15:02:29 <bh526r> #topic AOB
15:03:17 <bh526r> #info Trevor C will give update if Infrastructure comparison hosting v.s. service, and perhaps update of compliance program
15:03:23 <bh526r> #info Meeting adjourned
15:03:27 <bh526r> #endmeeting