18:00:40 #startmeeting tsc 18:00:40 Meeting started Thu Jan 18 18:00:40 2018 UTC. The chair is CaseyODL. Information about MeetBot at http://ci.openstack.org/meetbot.html. 18:00:40 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:40 The meeting name has been set to 'tsc' 18:00:47 #chair abhijitkumbhare skitt 18:00:47 Current chairs: CaseyODL abhijitkumbhare skitt 18:00:59 #topic Roll-call and agenda bashing 18:01:00 #info Brady Johnson 18:01:06 #info TSC members please info in 18:01:07 #info abhijitkumbhare 18:01:07 #info skitt 18:01:16 #info gzhao 18:01:25 #info anipbu 18:01:27 #info jamoluhrsen 18:04:44 #info LuisGomez 18:04:52 #info Welcome Quan to the TSC meeting 18:05:12 #info Thanh 18:05:47 #topic Agenda 18:05:49 https://wiki.opendaylight.org/view/TSC:Main#Agenda 18:07:03 #info bjohnson suggests we discuss the code freeze deadline 18:07:46 #action abhijitkumbhare to initiate an email thread regarding the Singularity Principle 18:08:08 #action CaseyODL to go write a straw-man/skeleton "How to get help" docs page in docs repo via Gerrit/Rst 18:08:23 #action rovarga to revive stalled discussions on TrieMap after he is back from the vacation 18:09:01 #action bjohnson to reach out to Maxime re. dlux and dluxapps and his involvement 18:09:36 #info bjohnson has already reached out 18:09:50 #undo 18:09:50 Removing item from minutes: 18:09:53 #undo 18:09:53 Removing item from minutes: 18:10:33 #info shague 18:10:46 #info rovarga 18:11:27 #topic TAC representative 18:11:36 Feel better! 18:11:55 +1 18:14:37 #info Options: 18:14:47 #info Option 1: The TSC Chair by default becomes the TAC representative 18:14:57 #info Option 2: Another member of the TSC is elected by the TSC 18:15:10 #info Option 3: Any interested committer approved by the TSC and elected by the TSC 18:16:05 #info Option 4: further discussion 18:16:09 [sorry for being late, but I'm here now] 18:16:37 #startvote Which option does the TSC prefer? 1, 2, 3, 4 18:16:37 Begin voting on: Which option does the TSC prefer? Valid vote options are 1, 2, 3, 4. 18:16:37 Vote using '#vote OPTION'. Only your last vote counts. 18:16:47 #vote 3 18:16:49 #vote 3 18:16:49 #vote 3 18:16:51 #vote 3 18:16:51 #vote 3 18:17:04 #vote 2 18:17:13 #vote 2 18:17:35 #vote 3 18:17:41 #vote 3 18:17:43 #vote 3 18:17:46 #vote 0 18:17:46 abhijitkumbhare: 0 is not a valid option. Valid options are 1, 2, 3, 4. 18:18:07 ah sorry I didn’t include an abstain option 18:18:37 #endvote 18:18:37 Voted on "Which option does the TSC prefer?" Results are 18:18:37 3 (8): gzhao, skitt, anipbu, LuisGomez, shague, lori, jamoluhrsen, zxiiro 18:18:37 2 (2): rovarga, bjohnson 18:19:02 #agreed The TAC representative shall be any interested committer approved by the TSC and elected by the TSC 18:19:14 #agreed Option 3 wins: Any interested committer approved by the TSC and elected by the TSC 18:19:19 #undo 18:19:19 Removing item from minutes: 18:21:52 #agreed One week self nomination period, followed by one week voting period 18:22:13 #topic Proposal for Releng Team to perform all version bumping activities 18:24:15 #info Most active projects have bumped to yangtools 2.0.0, LuisGomez has sent out projects that haven't 18:24:30 #info There is a fix in 2.0.1 yangtools that has critical fixes 18:24:48 #info LuisGomez is proposing LF do a version bump for projects already on 2.0.0 to 2.0.1 18:25:11 #info LuisGomez is not proposing LF bump projects to 2.0.0 if they haven't already 18:25:32 #info skitt and zxiiro talk about how we have agreed this for minor bumps in the past, and projects can opt out 18:26:15 #info there may be complex fixes required for going to 2.0.0, so projects would need to do that themselves LuisGomez says 18:26:20 #info two questions from rovarga 18:26:33 #info how can the patches be validated before the releng team merges them 18:27:48 #info what are the gating criteria before a patch is merged 18:28:48 #info LuisGomez is assuming that minor version bumps will not break projects, so minor version bumps should be okay whereas major version bumps would not be okay 18:29:49 #info dfarrell07 clarifies that TSC has authority to do this, it's not the case that the governance docs say they can't 18:33:17 #info LuisGomez and others don't think it's okay to wait on approval for all projects for all version bumps from odlparent and yangtoos to unbreak the world 18:34:46 #info shague says the world is broken now, so these patches need to get merged one way or another, project committer or someone else 18:35:39 #info all agree that going forward long term, gov docs need to change to make this situation more clear, deal with inactive projects not holding everyone else up 18:36:54 #info last time this was voted on it was about projects taking part in the SR bumping versions to release, this is different situation says rovarga 18:38:12 #startvote Does the TSC approve that the releng team can merge patches for the merge from yangtools 2.0.0 to yangtools 2.0.1, as long as they pass the verify job? -1, 0, +1 18:38:12 Begin voting on: Does the TSC approve that the releng team can merge patches for the merge from yangtools 2.0.0 to yangtools 2.0.1, as long as they pass the verify job? Valid vote options are -1, 0, +1. 18:38:12 Vote using '#vote OPTION'. Only your last vote counts. 18:38:56 #vote +1 18:38:57 #vote +1 18:38:59 #vote +1 18:39:00 #vote +1 18:39:01 #vote 0 18:39:02 #vote +1 18:39:03 #vote 0 18:39:10 #vote +1 18:39:32 Quan you can vote 18:39:32 #vote 0 18:39:36 #vote +1 18:39:46 Quan the vote is for: 18:39:49 https://www.irccloud.com/pastebin/4JfPKsEt/ 18:40:03 Quan: Does the TSC approve that the releng team can merge patches for the merge from yangtools 2.0.0 to yangtools 2.0.1, as long as they pass the verify job? Valid vote options are -1, 0, +1. 18:40:26 #endvote 18:40:26 Voted on "Does the TSC approve that the releng team can merge patches for the merge from yangtools 2.0.0 to yangtools 2.0.1, as long as they pass the verify job?" Results are 18:40:26 0 (3): skitt, rovarga, jamoluhrsen 18:40:26 +1 (7): bjohnson, anipbu, LuisGomez, shague, lori, abhijitkumbhare, zxiiro 18:40:40 +1 18:40:58 #info for the record, Quan voted +1 18:41:52 the mdsal bump is just finishing its merge job now 18:42:44 #topic Groups.io 18:42:57 dfarrell07, I’ll send an email about version ranges 18:43:28 #topic Oxygen 18:48:01 #info bjohnson and others are proposing an extension of code freeze to let offset two projects get changes in, since things have been very broken for quite some time (infra, version bumps) 18:48:02 #info pain in this release from the infra changes as well as the odlparent/yangtools bump 18:48:07 #undo 18:48:07 Removing item from minutes: 18:48:41 #info note: we actually held off the integration to get CSIT environment stabilized 18:49:28 #info shague thinks we will not be in good shape by the first RC date, rovarga thinks we should not have that RC if it is expected to be broken 18:50:26 #startvote Shall the TSC slip the code freeze and RC0 by one week? -1, 0, +1 18:50:26 Begin voting on: Shall the TSC slip the code freeze and RC0 by one week? Valid vote options are -1, 0, +1. 18:50:26 Vote using '#vote OPTION'. Only your last vote counts. 18:50:27 #info dfarrell07 hopes we will not have to slip release date 18:50:39 #info jamoluhrsen doesn't want us to steal test time at the end of all of this 18:50:40 #vote +1 18:52:56 #endvote 18:52:56 Voted on "Shall the TSC slip the code freeze and RC0 by one week?" Results are 18:52:56 +1 (1): abhijitkumbhare 18:53:05 #info Option 1: stick to the current release plan 18:53:14 #info Option 2: slip code freeze and RC0 by one week 18:53:25 #info Option 3: slip the rest of the release plan by one week 18:53:30 #info Option 0: abstain 18:53:32 +1 I fill it waste much time to merge odlparent bump 18:53:41 feel ,sorry 18:54:10 agreed Quan 18:54:40 #startvote Shall the TSC amend the planned dates on the release plan? 0, 1, 2, 3 18:54:40 Begin voting on: Shall the TSC amend the planned dates on the release plan? Valid vote options are 0, 1, 2, 3. 18:54:40 Vote using '#vote OPTION'. Only your last vote counts. 18:54:41 #vote 3 18:54:42 the actual merge has not taken a full week as of right now 18:54:45 #vote 0 18:54:47 #vote 3 18:54:48 #vote 3 18:54:50 #vote 3 18:54:52 #vote 3 18:54:53 rovarga, nearly a whole week though. 18:54:57 #vote 3 18:55:01 #vote 2 18:55:09 #vote 3 18:55:11 #vote 3 18:55:13 and it's not done, we still have to have 2.0.1 18:55:20 #vote 2 18:55:20 jamoluhrsen: yes, which included a weekend and Martin Luther King Day ;-) 18:55:33 rovarga, true. I did not work monday :) 18:55:40 Quan: Did you want to vote? 18:55:43 we had off monday?! 18:55:53 Really, I thought it was just the post office closed on MLK?? 18:55:59 vote 3 18:56:05 dfarrell07: jamoluhrsen: fair point, but in my experience ~5 work days to integrate ~20 projects on this scale is a pretty good statistic :) 18:56:14 Format is #vote OPTION 18:56:25 Quan - just add # before “vote” 18:56:33 rovarga, the controller failure is weird: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/controller-maven-javadoc-verify-oxygen/227/console.log.gz 18:56:34 #vote 3 18:56:36 rovarga: I just want to get this release refactoring done so we only have to care about a few active projects 18:56:39 #endvote 18:56:39 Voted on "Shall the TSC amend the planned dates on the release plan?" Results are 18:56:39 0 (1): gzhao 18:56:39 3 (9): rovarga, bjohnson, skitt, zxiiro, LuisGomez, Quan, jamoluhrsen, anipbu, abhijitkumbhare 18:56:39 2 (2): shague, lori 18:56:41 sorry casey 18:56:54 No problem. :) 18:56:59 #agreed the TSC slips the rest of the release plan by one week 18:57:07 I’ll have to drop in four minutes 18:57:10 three 18:57:15 #topic Carbon 18:57:21 #chair dfarrell07 18:57:21 Current chairs: CaseyODL abhijitkumbhare dfarrell07 skitt 18:57:39 skitt: hmm... looks nexus-y 18:57:51 #info klou has an RC out for Carbon SR3 18:57:52 rovarga, yes 18:58:13 #info jamoluhrsen has run CSIT against that Carbon SR3, results are in and klou is updating spreadsheet 18:58:13 skitt: recheck should take care of that :) 18:58:29 rovarga, done 18:58:37 #info jamoluhrsen wants us to vote now to release this RC as carbon SR3 if it passes netvirt tests, others seem sane 18:58:51 +1 18:59:00 #startvote Shall the TSC approve the latest Carbon release candidate as SR3 if it passes netvirt tests? -1, 0, +1 18:59:00 Begin voting on: Shall the TSC approve the latest Carbon release candidate as SR3 if it passes netvirt tests? Valid vote options are -1, 0, +1. 18:59:00 Vote using '#vote OPTION'. Only your last vote counts. 18:59:02 #vote +1 18:59:06 #vote +1 18:59:06 #vote +1 18:59:08 #vote +1 18:59:09 #vote +1 18:59:11 #vote +1 18:59:15 #vote 1 18:59:15 shague: 1 is not a valid option. Valid options are -1, 0, +1. 18:59:15 #vote +1 18:59:18 #vote +1 18:59:20 #vote 1 18:59:20 shague: 1 is not a valid option. Valid options are -1, 0, +1. 18:59:20 skitt: is a faster typer than me;) 18:59:24 #vote +1 18:59:29 #vote +1 18:59:34 #vote +1 18:59:39 #endvote 18:59:39 Voted on "Shall the TSC approve the latest Carbon release candidate as SR3 if it passes netvirt tests?" Results are 18:59:39 +1 (11): rovarga, bjohnson, skitt, anipbu, LuisGomez, shague, Quan, lori, abhijitkumbhare, zxiiro, jamoluhrsen 18:59:51 dfarrell07: not meaning to be offensive, but given that we have downstreams wathing our release -- isn't our slipping for Carbon SR3 problematic? 18:59:53 thanks skitt 19:00:07 you’re welcome jamoluhrsen ;-) 19:00:11 #topic ONS Developer Event 19:00:30 rovarga: yeah but not for overall sync with other projects like OPNFV and OpenStack 19:00:32 #info LFN wiki to be live soon 19:00:38 rovarga: those are sync'd on major releases 19:00:49 #info ODL DDF has to be on Sunday 19:01:12 is the lfn wiki, like our ddf wiki where we just post topics and someone makes a schedule? 19:01:15 dfarrell07: but I would assume they do need our fixes, don't they? 19:01:33 rovarga: yeah but they get them via CD pipelines mostly now 19:01:54 rovarga: they needed fixes way faster than SRs way long ago 19:02:01 bjohnson, just use the bar for your breakouts 19:02:02 rovarga: hence the XCI work we've been doing 19:02:16 breakin out at the bar 19:02:16 agree jamoluhrsen :) 19:02:23 rovarga: so I don't worry so much about SR timing, but do more about major release timing 19:02:39 dfarrell07: so wouldn't it actually make sense to brind those CD pipelines into ODL proper to manage inter-project things? 19:02:43 bjohnson: you jamoluhrsen and i can hang out at the bar :) 19:02:58 Abhijit, I can not attend the meeting in USA. Can I Join in you online? 19:02:59 rovarga: they are, odl-proper, that's Int/Pack 19:03:30 rovarga: https://nexus.opendaylight.org/content/repositories/opendaylight-oxygen-epel-7-x86_64-devel/org/opendaylight/integration-packaging/opendaylight/ 19:03:33 #agreed ODL DDF has to be on Sunday 19:03:38 rovarga: they are even on Nexus:) 19:03:41 dfarrell07: I mean... propagating fixes between, say, netconf and of-config, the same way we are pushing them from ODL to OPNFV 19:03:41 #undo 19:03:41 Removing item from minutes: 19:04:10 #agreed ODL DDF will be on Sunday March 25, 2018 19:04:17 rovarga: yeah, that's something for you kernel folks to figure out, very different challenges I think 19:04:40 dfarrell07: how different? 19:04:54 rovarga: I think they are mostly maven issues preventing that, right? 19:05:00 rovarga: I don't really know to be honest 19:05:13 #topic Groups.io 19:05:32 #action CaseyODL to send an email about Groups.io update 19:06:02 #info Any feedback to be provided over the email thread 19:06:18 dfarrell07: at the end of the day it boils down to a CD pipeline, which involves automatic git commits and nexus staging repos -- aside from that, I don't think there is anything special 19:06:24 #topic Cookies or Beer 19:06:45 rovarga: we should have a DDF topic 19:06:51 #info As usual 19:06:56 #endmeeting