17:00:12 #startmeeting tsc 17:00:12 Meeting started Thu Oct 8 17:00:12 2015 UTC. The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html. 17:00:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:12 The meeting name has been set to 'tsc' 17:00:18 #topic agenda bashing and roll call 17:00:24 TSC members, please #info in 17:00:27 #info colindixon 17:00:34 #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=37287#Agenda the agend in it's usual plce 17:01:19 #link https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-10-01-16.59.html last week's meeting minutes 17:01:37 #action colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade from Helium to Lithium (for SR3) https://bugs.opendaylight.org/show_bug.cgi?id=3160 17:01:55 #action colindixon to reach out to the advisory gorup for input on Boron 17:02:09 #info Daniel Farrell 17:02:16 #action alagalah to organize a panel/mailing list thead for the PTLs to also provide info on Boron 17:02:16 * dfarrell07 is still working on audio 17:02:26 #info Chris Price 17:02:29 #undo 17:02:29 Removing item from minutes: 17:02:30 #undo 17:02:30 Removing item from minutes: 17:02:40 #info Christ Price (for him since I undid it) 17:02:48 Christ? 17:02:53 #Undo 17:02:53 Removing item from minutes: 17:02:58 #info Christ Price (for him since I undid it) 17:03:02 #Undo 17:03:02 Removing item from minutes: 17:03:05 #info edwarnicke 17:03:08 #info Chris Price (for him since I undid it) 17:03:12 #info mohnish anumala 17:03:47 * dfarrell07 has audio 17:04:07 #info Kevin Luehrs (UNIMgr) 17:04:12 #undo 17:04:12 Removing item from minutes: 17:04:19 KLuehrs: typically only TSC members #info in 17:04:48 KLuehrs: Which is not to say we don't love you too ;) 17:04:49 OK sorry Colin 17:04:52 : ) 17:04:59 #topic updates 17:05:02 #undo 17:05:02 Removing item from minutes: 17:06:10 #topic TSC at-large Elections 17:06:55 for the record, I have a poor connection, so if I drop that's what's going on 17:07:27 #info colindixon describes the Board meeting held last night. Much discussion on the vote for the 17:07:36 #info LuisGomez 17:08:11 #info The Board felt that the waver was going to be approved indef if we don't come up with a better solution 17:08:20 #info waiver to allow Platinum designates to remain on TSC if/when other employees from the same company join the TSC 17:08:23 Do we simply take the feedback and waive the waiver from the TSC? 17:09:05 #info edwarnicke asks were any thoughts from the Board given? 17:09:53 #info colindixon notes that the Board felt that as long as platinum designates exist, the waiver will be needed. So finding ways to get rid of Platinum designates would be helpful 17:10:18 * ChrisPriceAB finds 18 to be an intersting # 17:10:26 #info edwarnicke asks do we have a sense of what a "minimal viable size" for the TSC?... the answer is "no" a minimum size was not discussed 17:11:06 I would want to have 7 for divesrity. 17:11:10 #info colindixon and edwarnicke not that "2 is too small and 18 is too big" 17:11:26 ChrisPriceAB: 7 is a number that feels good to me 17:11:37 ChrisPriceAB: I could be persuaded of other numbers in that general neighborhood 17:11:47 ChrisPriceAB: But 7 feels reasonable for a floor 17:12:02 If you don't want to cross the road you are talking 9 or 5... 17:12:13 :D 17:12:29 #info Phil or Neela will launch a thread to discuss this and possibly form a workgroup made up from Board and TSC members 17:12:36 #info Delaying the election process by 30 days doesn't cause a legal problem, says legal people 17:12:48 so they say... 17:13:56 #topic events 17:14:13 #link https://www.opendaylight.org/global-events the events page as usual 17:14:15 LSO hackfest... 17:14:26 #info SDN OF world congress in dusseldorf next week 17:14:42 #info hackfest near SF on 11/9 and 11/10, currently have 72 registered people, maxes out a 130, so register 17:14:53 * ChrisPriceAB thinks it maye be worth mentioning: https://wiki.mef.net/display/LH/MEF+LSO+Hackathon 17:14:55 #nof LSO hacakathon in Dalls on 11/16 17:15:02 #undo 17:15:02 Removing item from minutes: 17:15:10 #info hackfest near SF on 11/9 and 11/10, currently have 72 registered people, maxes out a 130, so register 17:15:13 nof nof 17:15:31 #link https://wiki.mef.net/display/LH/MEF+LSO+Hackathon LSO hacakathon in Dallas on 11/16 17:15:32 #link http://regonline.com/ODLHackfest2015 Hackfest reg site 17:15:47 ^^so we don't have an excuse 17:15:53 #topic Beryllum 17:16:02 * ChrisPriceAB likes excuses, they don't even need to be good. 17:16:32 #info we have 5 outstanding M3 readouts: l2swich, neutron, snmp, snmp4sdn, and yang-push 17:17:04 #info regXboi (ryant moats) notes that the neutron delay was because of other fires from upstream hurting them 17:18:52 #info anipbu is noting that we have started removing projects from beryllium from auto-release when they are blocking progress in addition to notifiying them of the issue 17:19:32 #info edwarnicke asks if we're removing projects from integration/distribution as well because it will fail to build if artifacts it dpeends on aren't built as part autorelese 17:21:42 #info colindixon notes that breaking autorelease should be similar to projects as if they couldn't run mvn and should treat it as such when helping out to fix things 17:22:15 #link https://wiki.opendaylight.org/view/Weather#Weather_Forecast external version upgrades are coming over time, look at weather here for more information 17:22:27 #undo 17:22:27 Removing item from minutes: 17:22:45 #link https://wiki.opendaylight.org/view/Weather#Current_Weather_Report external version upgrades are coming over time, look at weather here for more information 17:23:20 #info regXboi begs people to test everything first, and he notes that Eclipse 2.6.0 persistence broke things 17:23:23 https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=1314869162 17:24:00 #link https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=1314869162 anipbu notes that Steven has been building locally to see how patches affect all projects for external dependencies 17:24:38 #info edwarnicke asks if we have a way to test this automatically, colindixon says we do for single patches 17:25:45 #link https://nexus.opendaylight.org/content/sites/site/org.opendaylight.releng.builder/master/jenkins.html#Patch_Test_Job this works for single patches, but this doesn't work for parten poms around odlparent since parent poms are included at build time, not assembly time 17:28:31 #info rovarga says that we could move the odlparent dependency managment to an artifacts-style pom which could then be imported into other proejcts, this would mean that we could change versions at assembly time, not build time, which would allow the patch test job to work (but not for properties) 17:29:51 #info for what it's worth if you get old versions if you pull in external bundles by version in karaf features.xml, instead odlparent could publish them as features as well 17:31:44 colindixon: it's pretty late in the day for skitt, 8:30PM I think 17:32:30 #action anipbu to work with others (stephen kitt?) to see if we can get this done, move odlparent dependency managment to an artifacts pom, move away from odlparent properties, and make third party bundles features in odlparent 17:33:43 * edwarnicke thinks we need to find a way to reward skitt... 17:34:05 edwarnicke: tell cdub, he has $$$ rewards ;) 17:35:23 #info regXboi asks when we push go for an upgrade based on anipbu's spreadsheet above 17:35:38 #info anipbu says when all projects have been contacted and agree or have no failures 17:35:48 #info LuisGomez asks what about projects with not enough system tests 17:36:23 correction: if there are breakages, the projects will be contacted. 17:36:34 #chair anipbu 17:36:34 Current chairs: anipbu colindixon 17:36:43 anipbu: feel free to #undo and fix 17:38:18 #undo 17:38:18 Removing item from minutes: 17:38:21 #undo 17:38:21 Removing item from minutes: 17:38:48 #info anipbu says that all projects with breakages are contacted and when to proceed is based on people's responses 17:38:54 #info LuisGomez asks what about projects with not enough system tests 17:40:28 #info LuisGomez asks if we need to get all projects to vote +1 on a new patche to merge it, colindixon says that with 50 projects and the numer of external versions we need to ugrade, we don't have time to take a week to collect feedback from each project 17:42:44 #info rovarga notes that the changes to odlparent are likely to have to wait until Boron because offset 0 M4 is a week from now 17:43:23 #info regXboi asks if we should have a designed time between releases to line up the new build chains and things like like that before the major development happens 17:44:52 #topic Isaku Yamahata to committer for Neutron Northbound 17:45:05 #link https://lists.opendaylight.org/pipermail/tsc/2015-October/003943.html Request mail to TSC ML 17:45:11 #link https://lists.opendaylight.org/pipermail/neutron-dev/2015-October/000416.html NN vote thread 17:45:17 #link https://git.opendaylight.org/gerrit/#/q/project:neutron patch sets 17:45:35 Did we skip over Lithium Topic? 17:45:39 #info he is #2 committer in terms of patch sets in last 90 days and has been handling a lot of testing and bug fixing 17:45:51 anipbu: are we ready to vote on Lithium-SR2? 17:45:54 that will be next 17:46:32 #startvote shall the TSC confirm Isaku Yamahata as a committer for Neutron Northbound? -1, 0, +1 17:46:32 Begin voting on: shall the TSC confirm Isaku Yamahata as a committer for Neutron Northbound? Valid vote options are -1, 0, +1. 17:46:32 Vote using '#vote OPTION'. Only your last vote counts. 17:46:36 #vote +1 17:46:37 #vote +1 17:46:38 #vote +1 17:46:38 #vote +1 17:46:38 #vote +1 17:46:39 #vote +1 17:46:43 #vote +1 17:46:52 #endvote 17:46:52 Voted on "shall the TSC confirm Isaku Yamahata as a committer for Neutron Northbound?" Results are 17:46:52 +1 (7): jmedved, LuisGomez, dfarrell07, ChrisPriceAB, edwarnicke, colindixon, mohnish_ 17:47:05 #topic Lithium-SR2 17:47:22 #info we are still waiting on the controller team to sign off that the test failures are non-blocking 17:48:03 #link https://docs.google.com/spreadsheets/d/1ktL11ElNdf4D3RUeRNUd8SPnYO0to0DxzSZGst0KdMQ/edit#gid=599953319 17:48:05 https://docs.google.com/spreadsheets/d/1ktL11ElNdf4D3RUeRNUd8SPnYO0to0DxzSZGst0KdMQ/edit#gid=599953319 17:49:32 #info tom pantelis is looking at the clustering ones, and ttkacik is looking at teh netconf one 17:50:08 #info LuisGomez says the clustering ones aren't regressions 17:50:18 #info LuisGomez beileves that the netconf one is also not a regression 17:53:14 #info ttkacik says that it looks like we have conflicts related to open ports (in this case it looks line oneM2M was binding to a port in use) in the NETCONF failures 17:54:17 #action anipbu to talk to ttkacik to for help with figuring out which projects are conflicting with prots and try to resolve (or at least document) 17:56:54 #startvote shall the TSC approve the Lithium-SR2 release using the artifacts tested as described in anipbu's spreadsheet linked above? -1, 0, +1 17:56:54 Begin voting on: shall the TSC approve the Lithium-SR2 release using the artifacts tested as described in anipbu's spreadsheet linked above? Valid vote options are -1, 0, +1. 17:56:54 Vote using '#vote OPTION'. Only your last vote counts. 17:57:13 #vote +1 17:57:14 #vote +1 17:57:16 #vote +1 17:57:18 #vote +1 17:57:22 #vote +1 17:57:24 #vote +1 17:57:32 #endvote 17:57:32 Voted on "shall the TSC approve the Lithium-SR2 release using the artifacts tested as described in anipbu's spreadsheet linked above?" Results are 17:57:32 +1 (6): jmedved, LuisGomez, ChrisPriceAB, dfarrell07, edwarnicke, colindixon 17:57:46 #agree we will ship the LIthium-SR2 artifacts 17:58:19 #action anipbu to get tykeal_away the staging repo number, and talk with zxiiro to get the versions bumped 17:58:29 #topic Beryllium branch cutting 17:58:46 #link https://lists.opendaylight.org/pipermail/tsc/2015-September/003879.html the discussion 17:58:58 #info this needs to be decided by next week 18:00:13 +1 to colindixon’s suggestion of offset 2 M5 18:01:21 #info colindixon says that he'd like to see us cut all at once at offset 2 M5, which would be 12/17/2015, he knows it causes some people pain, but that it tends to cause pain for those who can bear it and will risk less breakage in offset 1 and offset 2 projects 18:03:36 #info rovarga notes that will effectively steal 5 weeks of development time from the offset 0 projects 18:04:56 #topic cookies 18:05:28 #endmeeting