17:04:40 <CaseyODL> #startmeeting tsc
17:04:40 <odl_meetbot> Meeting started Thu Jul  6 17:04:40 2017 UTC.  The chair is CaseyODL. Information about MeetBot at http://ci.openstack.org/meetbot.html.
17:04:40 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:04:40 <odl_meetbot> The meeting name has been set to 'tsc'
17:04:40 <odl_meetbot> skitt: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.
17:04:57 <CaseyODL> #chair phrobb anipbu
17:04:57 <odl_meetbot> Current chairs: CaseyODL anipbu phrobb
17:05:58 <CaseyODL> #link https://wiki.opendaylight.org/view/TSC:Main#Agenda TSC Agenda
17:06:07 <CaseyODL> #topic Agenda bashing
17:06:36 <LuisGomez> #info LuisGomez
17:06:42 <jamoluhrsen> #info jamoluhrsen
17:06:46 <skitt> #info skitt
17:06:54 <anipbu> #info anipbu
17:06:56 <LuisGomez> #info LuisGomez for Abhijit too
17:06:58 <jamoluhrsen> LuisGomez, wait, the meeting isn't started
17:07:14 <LuisGomez> it has
17:07:24 <zxiiro> #info Thanh
17:07:27 <edwarnicke> #info edwarnicke
17:07:37 <rovarga> #vote rovarga
17:07:43 <rovarga> #info rovarga
17:07:44 <rovarga> :)
17:07:46 <huan> #info huan
17:07:48 <jamoluhrsen> :)
17:09:39 <jamoluhrsen> #topic release manager
17:09:46 <CaseyODL> #chair jamoluhrsen
17:09:46 <odl_meetbot> Current chairs: CaseyODL anipbu jamoluhrsen phrobb
17:09:58 <skitt> jamoluhrsen, you need to do that again
17:10:07 <CaseyODL> #link https://lists.opendaylight.org/pipermail/tsc/2017-June/007505.html Release manager discussion
17:10:07 <jamoluhrsen> #topic release manager
17:10:09 <vishnoianil> #info Anil Vishnoi
17:10:19 <skitt> the minutes are going to be interesting ;-)
17:10:23 <vishnoianil> is colin not joining today? I thought he was planning to stay around for some more time :-)
17:10:37 <jamoluhrsen> #info we need to find a new release manager, but no volunteers as of yet
17:10:39 <LuisGomez> he is in pto
17:11:24 <vishnoianil> oh okay.
17:11:56 <jamoluhrsen> #info jamoluhrsen asks if there is a way to dedicate a resource from the LF. release manager is a vital position that would be tough to live without
17:12:07 <edwarnicke> https://wiki.opendaylight.org/view/IRC
17:13:18 <jamoluhrsen> #info this topic has been escalated to the board, but not all companies are represented on the board
17:14:53 <jamoluhrsen> #info it could be best if the board itself could reach out to all the member companies asking for a dedicated release manager
17:15:49 <jamoluhrsen> #action CaseyODL to add this release manager position be made a priority for the next board meeting
17:17:11 <jamoluhrsen> #topic future DDF
17:17:14 <CaseyODL> #link https://lists.opendaylight.org/pipermail/tsc/2017-June/007506.html Discussion regarding the Future DDFs.
17:18:22 <jamoluhrsen> #info a poll was created to try to determine the reasons people do or do not come to DDF in order to better plan future DDFs. only 24 responses so far, so we'll wait another week
17:19:17 <CaseyODL> #link https://goo.gl/forms/1aho8rZy8WAqVNyN2 Link to DDF Poll.
17:20:43 <jamoluhrsen> #info rovarga suggests the poll go to other dev lists (e.g. controller) and wait until the end of the month before looking at results
17:21:48 <jamoluhrsen> #topic carbon support status
17:22:02 <CaseyODL> #link http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_b61348bdd2b0c06d Vote results for Carbon Support
17:23:01 <jamoluhrsen> #link https://lists.opendaylight.org/pipermail/tsc/2017-July/007638.html <-- email vote from LuisGomez anipbu skitt
17:23:59 <LuisGomez> jamoluhrsen, i voted in the tool
17:24:14 <jamoluhrsen> LuisGomez, what tool?
17:24:37 <zxiiro> huan: Do you have an opinion on https://lists.opendaylight.org/pipermail/tsc/2017-July/007638.html
17:24:39 <LuisGomez> the CIVS
17:24:48 <jamoluhrsen> LuisGomez,  that is for the ddf
17:24:59 <jamoluhrsen> this is for carbon support
17:25:05 <huan> i will vote for 12/15
17:25:13 <jamoluhrsen> LuisGomez, ignore me.
17:25:15 <jamoluhrsen> :)
17:25:36 <jamoluhrsen> #info huan has voted 12/15 for carbon support
17:25:44 <skitt> which is actually 9/15
17:25:44 <CaseyODL> #info huan votes for Release-based skipping Nitrogen, have Carbon get 9 months of bug fixes (until Oxygen is released on or about March 7th, 2018) and 15 months of security fixes (until Fluorine is release on or about September 7th, 2018)
17:25:53 <skitt> it's all Colin's fault
17:26:01 <rovarga> as usual :-D
17:26:04 <skitt> heh
17:26:14 <skitt> the two rules of TSC are
17:26:17 <skitt> vote for rovarga
17:26:22 <CaseyODL> #agree The TSC shall support Carbon for 9 months of bug fixes and 15 months of security fixes.
17:26:22 <skitt> and it's all colindixon's fault
17:26:24 <rovarga> skitt: :-D
17:26:43 <jamoluhrsen> #topic events
17:27:30 <jamoluhrsen> i missed the date/name of this cablelabs event if someone can put it in the notes
17:27:53 <jamoluhrsen> #info opensource summit NA and europe all coming soon
17:28:22 <jamoluhrsen> #action CaseyODL to send an email about cablelabs event, or at least get it on the wiki
17:28:31 <CaseyODL> #link http://www.cablelabs.com/event/summer-conference-2017/ CableLabs Event
17:28:54 <jamoluhrsen> #topic carbon
17:28:59 <anipbu> #link https://wiki.opendaylight.org/view/Simultaneous_Release/Carbon/SR1/Status   <— We initially targeted Carbon SR1 Release on 7/6, but we had to respin a new build to incorporate fixes in for blocker bugs in NETVIRT.
17:29:14 <anipbu> #link https://bugs.opendaylight.org/show_bug.cgi?id=8793   <— Blocker Bug in Carbon SR1 in NETVIRT: Many Null Pointer Exceptions for NAT and ACL Services seen on Carbon CSIT runs
17:29:28 <jamoluhrsen> third rule of tsc. netvirt always blocks the release
17:29:30 <anipbu> #link https://bugs.opendaylight.org/show_bug.cgi?id=8805  <— Cluster member gets in bad state if 2 instances disconnect just after the 3rd is recovered
17:29:50 <huan> haha
17:29:56 <jamoluhrsen> #topic nitrogen
17:30:05 <anipbu> #link https://git.opendaylight.org/gerrit/#/c/59718/   <- Plans to release ODLPARENT 2.0.2
17:30:17 <anipbu> #info Not all projects have to migrate to ODLPARENT 2.0.2.
17:30:50 <anipbu> #link https://docs.google.com/spreadsheets/d/1MYyGLFWN2RzUkJl8XMzXQ-3zWuOrUCQpIS6ORbmf4_U/edit#gid=188095956   <- We have successfully add all Kernel projects to Nitrogen Autorelease and Kernel projects have successfully migrated to Karaf 4
17:30:56 <rovarga> skitt: are you sure the above is true?
17:31:19 <skitt> rovarga, pretty sure, we only need aaa and netconf on 2.0.1 for bouncycastle, and int/dist on 2.0.2 for the karaf scripts stuff
17:31:21 <rovarga> features have versions -- will it not conflict?
17:31:32 <anipbu> #info We are only one week behind in Karaf 4 Migration
17:31:57 <skitt> rovarga, they shouldn't since odlparent versions are still within the same major
17:32:15 <skitt> rovarga, I'll test that in detail tomorrow
17:32:19 <rovarga> but they are referenced in downstream features, won't they reinstall things?
17:33:09 <rovarga> notebly odl-netty-4
17:36:07 <jamoluhrsen> #info we still need to confirm if all projects need to be on odlparent 2.0.2 or if we can have a mix of versions 2.0.x
17:36:11 <skitt> rovarga, the refreshes are actually decided at the bundle level, not the feature level
17:36:28 <skitt> rovarga, so since all the feature versions contain the same bundles currently, apart from bouncycastle...
17:36:51 <skitt> rovarga, we should be OK
17:37:36 <rovarga> skitt: right, but if netconf's feature requires odl-netty-4-2.0.2 and bgpcep's requires odl-netty-4-2.0.1, will concurrent feature:install work ?
17:37:42 <jamoluhrsen> #info if all projects must be on 2.0.2, we can ask projects to opt-in for an auto version bump
17:38:02 <jamoluhrsen> #info projects not in int/dist by m5 (1 month from now) will not be in the nitrogen release
17:38:08 <rovarga> I mean feature:install odl-restconf odl-bgpcep-bgp-all (or whatever the names are)
17:38:14 <jamoluhrsen> #topic infrastructure
17:38:16 <skitt> rovarga, that's what I need to check tomorrow
17:38:19 <jamoluhrsen> #info no updates
17:38:25 <skitt> rovarga, it should be OK because all the features will resolve to the same bundles
17:38:28 <jamoluhrsen> #topic int/test
17:38:32 <jamoluhrsen> #info no updates
17:40:06 <jamoluhrsen> #topic security mailing list
17:41:31 <skitt> #link security wiki https://wiki.opendaylight.org/view/Security:Main
17:41:40 <skitt> #action skitt to update the security wiki
17:41:58 <skitt> that's the page that says "on ... the TSC added ..."
17:43:13 <anipbu> #startvote shall the TSC add skitt as a member of the security response team? -1,0,+1
17:43:13 <odl_meetbot> Begin voting on: shall the TSC add skitt as a member of the security response team? Valid vote options are -1, 0, +1.
17:43:13 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
17:43:57 <rovarga> #note +1
17:43:59 <vishnoianil> #vote +1
17:44:01 <zxiiro> #vote +1
17:44:01 <anipbu> #vote +1
17:44:04 <edwarnicke> #vote +1
17:44:06 <jamoluhrsen> #vote +1
17:44:06 <rovarga> #vote +1
17:44:08 <LuisGomez> #vote +1
17:44:29 <skitt> #vote +1
17:44:32 <skitt> ;-)
17:44:35 <rovarga> :-D
17:44:39 <CaseyODL> huan: Can you vote please?
17:44:42 <anipbu> ping huan
17:44:48 <skitt> and we can add an item to the next TSC agenda to clarify this whole voting thing
17:45:03 <huan> #vote +1
17:45:09 <anipbu> #endvote
17:45:09 <odl_meetbot> Voted on "shall the TSC add skitt as a member of the security response team?" Results are
17:45:09 <odl_meetbot> +1 (9): rovarga, skitt, zxiiro, LuisGomez, edwarnicke, jamoluhrsen, anipbu, huan, vishnoianil
17:45:18 <anipbu> #agreed skitt is a member of the security release team unanimously
17:45:29 <vishnoianil> Congrates! skitt ;)
17:45:40 <LuisGomez> congrats skitt
17:45:48 <anipbu> congrats skitt
17:45:50 <jamoluhrsen> sorry skitt
17:45:52 * edwarnicke feels more secure already
17:46:12 <skitt> does helpdesk deal with the subscription, or does the security team handle it internally?
17:46:24 <rovarga> skitt: helpdesk
17:46:33 <skitt> rovarga, same for the private bugzilla I guess
17:46:53 <rovarga> yup, it's a group membership thing
17:54:17 <CaseyODL> #topic cookies
17:54:24 <jamoluhrsen> #endmeeting