18:01:30 #startmeeting tsc 18:01:30 Meeting started Thu Dec 21 18:01:30 2017 UTC. The chair is skitt. Information about MeetBot at http://ci.openstack.org/meetbot.html. 18:01:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:01:30 The meeting name has been set to 'tsc' 18:01:32 #chair CaseyODL 18:01:32 Current chairs: CaseyODL skitt 18:01:41 #chair abhijitkumbhare bjohnson 18:01:41 Current chairs: CaseyODL abhijitkumbhare bjohnson skitt 18:01:48 #topic Agenda bashing 18:01:53 #info TSC members please info in 18:01:57 #info skitt 18:01:57 #info Brady Johnson 18:02:00 #info gzhao 18:02:29 #info abhijitkumbhare 18:02:33 #info anipbu 18:04:44 Original vote pinned to PST time zone: https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-12-15-18.01.html 18:06:59 has the TSC chair vote concluded? 18:07:07 dfarrell07, I don’t think so 18:07:14 you folks are slow af 18:07:15 vote! 18:08:11 * skitt voted last week 18:08:20 * dfarrell07 thanks skitt 18:08:52 CaseyODL, you’re not displaying the usual pre-meeting notice 18:09:11 I already did. 18:09:15 oh sorry 18:09:19 :) 18:09:22 oh yes we’re recording 18:09:34 #info jamoluhrsen 18:10:00 lori shague 18:10:12 LuisGomez too 18:10:32 lori and shague aren’t on the call 18:12:40 #info LuisGomez 18:12:59 #info Anil Vishnoi 18:13:21 #startvote Who will be present for next week's TSC call (APAC)? -1, +1 18:13:21 Begin voting on: Who will be present for next week's TSC call (APAC)? Valid vote options are -1, +1. 18:13:21 Vote using '#vote OPTION'. Only your last vote counts. 18:13:27 #vote -1 18:13:31 #vote +1 18:13:33 #vote -1 18:13:36 #vote -1 18:13:41 #vote -1 18:13:45 #vote -1 18:13:49 +1 18:13:49 #vote +1 18:13:58 #vote +1 18:14:28 #endvote 18:14:28 Voted on "Who will be present for next week's TSC call (APAC)?" Results are 18:14:28 +1 (3): gzhao, abhijitkumbhare, anipbu 18:14:28 -1 (5): skitt, LuisGomez, vishnoianil, jamoluhrsen, bjohnson 18:14:56 #info Very little participation in APAC meetings anyway, including from APAC members 18:15:12 #info Perhaps we should only hold APAC meetings when requested 18:15:46 #action bjohnson to reach out to APAC members to ask them if they would like an APAC meeting in the first week of January 18:16:35 #undo 18:16:35 Removing item from minutes: 18:17:16 #action bjohnson to reach out to APAC members to see whether they want to continue the APAC meetings and in what form 18:18:36 #info Last meeting only had six people join 18:18:46 #info (last APAC meeting) 18:18:58 #info We hardly ever meet quorum for APAC calls 18:19:33 #info We could just cancel next week’s meeting outright anyway 18:20:49 #agreed Next week’s TSC meeting is cancelled (December 28) 18:21:10 #action CaseyODL to remove the calendar entry for next week’s meeting 18:22:09 #info The next TSC meeting will be on January 4 at the usual time 18:22:23 #info The next APAC call will be at the end of January as usual (for the time being) 18:23:14 #topic Events 18:25:26 #info Nothing new, next big event is at ONS, with an ODL DDF 18:25:56 #info CaseyODL confirms ODL DDF at ONS will be at start of event, not end, so doesn't conflict with passover on Friday 18:26:27 #action CaseyODL to pressure LF leadership folks to get invites to LF Leadership Summit out ASAP so folks can plan budget 18:26:57 #info unclear yet whether the ODL DDF will take place before ONS (the previous Friday or over the weekend) or concurrently with the start of ONS 18:28:03 #info There will also be a cross-project CI/CD mini-summit 18:28:11 #topic Oxygen 18:28:17 #link https://wiki.opendaylight.org/view/Release_Dashboard 18:28:51 That’s neat dashboard klou :) 18:29:26 shague: we're about to talk about Netvirt bugs in Carbon and if they are blockers, what to do about release 18:33:28 #action New TSC Chair to follow up with new NetConf PTL about situation, adding new committers, it has been the week they requested 18:34:27 dfarrell07: Im going to reach out to Jakub Morvay today 18:35:05 #info vishnoianil points out that if Netconf can't get back to TSC in timely manner it seems very likely they can't follow up with community 18:35:27 #info if new NetConf PTL doesn't reply with plans to get project healthy by TSC meeting 1/4 18:37:46 #info the lack of updates from yangtools, mdsal etc. raises the question of what to do with projects with a bus factor of 1 18:38:27 #info the wiki suggests there are quite a few committers, which seems to be inaccurate 18:38:31 #info LuisGomez points out that there are lots of committers on yangtools wiki, that it's not okay to have this disconnect between wiki and reality 18:39:02 * tykeal notes that of the the yangtools committers only robert actually accepted the invite into the new ACL group 18:39:21 #info vishnoianil wants projects to update committer list so TSC can accurately judge health of project 18:39:45 #info we need to ask projects who is active, and provide a definition of active 18:39:52 #info skitt points out that they are therefore not correctly reporting "wiki up to date" 18:40:07 #info we need to compare the official list of committers on the wiki with real levels of activity 18:40:42 #info dfarrell07 thinks as a part of new release model we will have chance to put better requirements about what "active" means, what to do if project is unhealthy 18:40:43 #info a big list of inactive committers on the wiki also discourages new contributors 18:40:48 dfarrell07++ 18:44:15 #topic Nitrogen 18:44:19 maybe we should schedule a special TWS session to specifically discuss this topic? 18:44:24 klou: just start talking when you get a chance ;_ 18:44:34 :) 18:45:01 #info We did not release SR2 on December 7 18:45:02 agree anipbu 18:45:22 #info recommendation is just to merge SR2 and SR3, and release on February 7 18:45:37 #action CaseyODL to add "healthy project/committer" discussion to TWS agenda 18:45:46 we should vote 18:45:48 #startvote Shall we release SR2 on February 7, 2018, merging SR2 and SR3? -1, 0, +1 18:45:48 Begin voting on: Shall we release SR2 on February 7, 2018, merging SR2 and SR3? Valid vote options are -1, 0, +1. 18:45:48 Vote using '#vote OPTION'. Only your last vote counts. 18:45:54 #vote +1 18:45:55 #vote +1 18:45:56 #vote +1 18:46:03 #vote +1 18:46:06 #vote +1 18:46:06 #vote +1 18:46:11 #vote +1 18:46:14 #vote +1 18:46:17 see, i do vote 18:46:19 #endvote 18:46:19 Voted on "Shall we release SR2 on February 7, 2018, merging SR2 and SR3?" Results are 18:46:19 +1 (8): gzhao, bjohnson, skitt, LuisGomez, jamoluhrsen, anipbu, vishnoianil, abhijitkumbhare 18:46:22 jamoluhrsen: ;) 18:46:33 #agreed We will release Nitrogen SR2 on February 7, 2018, merging SR2 and SR3 18:46:40 jamoluhrsen :) 18:46:48 #info SR3 will be planned for May 7 18:47:57 #info No planned SR4 now 18:48:05 #topic Carbon 18:48:18 #info SR3 planned to be released last week 18:48:27 #info we have a RC, had to re-run CSIT a couple of times 18:48:39 #info there are 45 failures, all of which have been reviewed 18:48:44 #info thanks to jamoluhrsen and LuisGomez 18:48:55 #info 9 remain to deal with, 3 of which appear to be regressions in NetVirt 18:49:13 #info those bugs will be moved to blocker state, and NetVirt will have to decide what to do 18:49:45 #action shague to decide if three Carbon SR3 regressions are blockers, and if so find someone to fix, else move out of bokcer state 18:50:02 #info Carbon SR3 is liable to be released only in January 18:54:19 #action vishnoianil to push netvirt bugs, either confirm blockers or help find/push folks to fix 18:55:34 #undo 18:55:40 skitt: can you undo 18:55:43 * dfarrell07 isn't chair 18:55:46 #undo 18:55:46 Removing item from minutes: 18:55:47 #undo 18:55:47 Removing item from minutes: 18:56:01 Sorry - race condition dfarrell07 :) 18:56:02 #info Carbon SR3 is liable to be released only in January 18:56:06 #topic Infrastructure 18:57:16 #info We will soon be completely switched over to the new Nexus system, which should resolve download speed issues 18:57:25 #info logs are being rsync'd over, sorry impossible to get to old logs for now 18:58:03 #info The quick clone issue should be resolved soon, except for projects using submodules 18:58:17 #info there is a git mirror in our new cloud that mirrors main git in AWS, that makes clones work but some types of interactions with Gerrit are still very slow/don't work at all 18:58:38 #info dfarrell07 has seen curls of small files from old gerrit just fail, TSC timeout 18:58:44 #undo 18:58:52 #info dfarrell07 has seen curls of small files from old gerrit just fail, TCP timeout 18:59:44 #info The vendor also have various tweaks in the wings to help fix speed issues 19:00:25 #topic Cookies 19:00:30 #endmeeting