18:00:36 <colindixon> #startmeeting tsc 18:00:36 <odl_meetbot> Meeting started Thu Feb 4 18:00:36 2016 UTC. The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html. 18:00:36 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:36 <odl_meetbot> The meeting name has been set to 'tsc' 18:00:42 <colindixon> #topic agenda bashing and roll call 18:00:50 <colindixon> #chair anipbu phrobb- 18:00:50 <odl_meetbot> Current chairs: anipbu colindixon phrobb- 18:01:07 <colindixon> #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=41044 the agenda in it's usual place 18:01:11 <mohnish_> #info mohnish anumala 18:01:17 <ttkacik> #info ttkacik as stand-in for eaw 18:01:23 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-01-28-18.00.html last week's meeting minutes 18:01:29 <colindixon> #info colindixon 18:01:34 <abhijitkumbhare> #info abhijitkumbhare stand-in for ChrisPriceAB 18:01:56 <colindixon> #action colindixon to keep boron planning on our minds 18:01:56 <colindixon> #action colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron? 18:01:57 <colindixon> #action colindixon to follow this issue to figure out lessons learned and how to avoid the two diffenent openflow plugin in the future 18:02:49 <LuisGomez> #info LuisGomez 18:03:04 <colindixon> #info colindixon asks about jdk8 and equinox, rovarga says that there are still 4-5 projects to move 18:03:06 <rovarga> #info rovarga for jmedved 18:03:10 <dfarrell07> #info Daniel Farrell 18:03:15 <anipbu> https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=1156234389 18:03:38 <colindixon> #Info rovarga says we already merged the move to jdk8 so they can merge their patfches then, anipbu is tracking that and says it only 3 projects now 18:04:12 <colindixon> #link https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=1156234389 this tracks jd8 progrees (column E tracks the equinox part) 18:04:36 <colindixon> #info rovarga says that jdk8 update 40 is required to get things to work with Boron builds and running 18:05:07 <colindixon> #action phrobb will make sure the mini-summit is on the events page (as more than just something hidden on the ONS page) 18:06:12 <colindixon> #topic tsc mailing list votes and discussion 18:06:29 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-February/004631.html updated best practices paragraph for avoid cross-project breakages 18:06:55 * dfarrell07 is fine voting now 18:07:27 * dfarrell07 has reviewed it, ready to vote 18:07:30 <colindixon> #startvote shal the tsc adopt the following best practices for preventing/handling cross-project breakages https://lists.opendaylight.org/pipermail/tsc/2016-February/004631.html? -1, 0, +1 18:07:30 <odl_meetbot> Begin voting on: shal the tsc adopt the following best practices for preventing/handling cross-project breakages https://lists.opendaylight.org/pipermail/tsc/2016-February/004631.html? Valid vote options are -1, 0, +1. 18:07:30 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts. 18:07:34 <abhijitkumbhare> Yes - reviewed it 18:07:41 <rovarga> #vote +1 18:07:44 <colindixon> #vote +1 18:07:44 <dfarrell07> #vote +1 18:07:47 <abhijitkumbhare> #vote +1 18:07:49 <ttkacik> #vote +1 18:07:51 <mohnish_> #vote +1 18:07:55 <LuisGomez> #vote +1 18:08:03 <colindixon> #endvote 18:08:03 <odl_meetbot> Voted on "shal the tsc adopt the following best practices for preventing/handling cross-project breakages https://lists.opendaylight.org/pipermail/tsc/2016-February/004631.html?" Results are 18:08:03 <odl_meetbot> +1 (7): rovarga, LuisGomez, dfarrell07, colindixon, ttkacik, mohnish_, abhijitkumbhare 18:08:24 <colindixon> #agree this is the TSC-endorsed best practices for preventing/handling cross-project breakages https://lists.opendaylight.org/pipermail/tsc/2016-February/004631.html 18:08:39 <colindixon> #topic TSC Elections 18:09:10 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-February/004633.html colin's asks for votes questions around the election 18:09:36 <colindixon> #info edwarnicke and dfarrell07 felt we could vote #1 (the framework), but hesitant to vote on #2 or #3 18:09:57 <colindixon> #info dfarrell07 says there are still some details, but the framework seems sane 18:10:17 <colindixon> #info dfarrell07 would like some preliminary endorsement to go off to figure out how the voting will mechanically work 18:10:48 <colindixon> #link https://wiki.opendaylight.org/view/TSC:Election_Proposal this is the framework (well really everything up to Represented Group Proposals) 18:11:59 <colindixon> #info colindixon says we are required to have annual elections by our charter, the last election was in October of 2014, so we're at ~16 months 18:12:21 <colindixon> #info colindixon asks if it's reasonable to work out the details now and go for it or wait until next time and have normal elections now 18:13:52 <colindixon> #startvote shall the TSC preliminarily adopt the new framework for TSC elections (see https://wiki.opendaylight.org/view/TSC:Election_Proposal ) either for this election or the one after, which does address the board request? -1, 0, +1 18:13:52 <odl_meetbot> Begin voting on: shall the TSC preliminarily adopt the new framework for TSC elections (see https://wiki.opendaylight.org/view/TSC:Election_Proposal ) either for this election or the one after, which does address the board request? Valid vote options are -1, 0, +1. 18:13:52 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts. 18:15:51 <dfarrell07> #vote +1 18:15:51 <LuisGomez> #vote +1 18:15:55 <colindixon> #vote +1 18:16:17 <rovarga> #vote +1 18:16:31 <mohnish_> #vote +1 18:16:34 <abhijitkumbhare> #vote +1 18:16:48 <ttkacik> #vote +1 18:17:07 <colindixon> #endvote 18:17:07 <odl_meetbot> Voted on "shall the TSC preliminarily adopt the new framework for TSC elections (see https://wiki.opendaylight.org/view/TSC:Election_Proposal ) either for this election or the one after, which does address the board request?" Results are 18:17:07 <odl_meetbot> +1 (7): rovarga, LuisGomez, dfarrell07, colindixon, ttkacik, abhijitkumbhare, mohnish_ 18:17:19 <colindixon> #info #info we can take this to the board to get the waiver to run this election as we see fit new style or old style, the next election must be some new style, we will vote later what we want this election to be 18:17:42 <colindixon> #agree the TSC preliminarily adopts the new framework for TSC elections (see https://wiki.opendaylight.org/view/TSC:Election_Proposal ) either for this election or the one after, which does address the board request 18:18:19 <colindixon> #action phrobb- to take the vote about new election styles to the board to enable renewal of the platinum designate waiver (via e-mail) 18:18:20 * rovarga notes there seems to be spreading confusion about TSC/board :) 18:18:55 <colindixon> #topic events 18:19:02 <colindixon> #link https://www.opendaylight.org/global-events 18:19:18 <colindixon> we may have lost phrobb- 18:19:50 <colindixon> #link https://www.opendaylight.org/events/2016-02-29-000000-2016-03-01-000000/opendaylight-developer-design-forum developer design form on 2/29-3/1, CFP is out, please submit 18:20:02 <colindixon> #info phrobb- will make a wiki page of the topics after that closes for us to plan 18:20:11 <colindixon> #info there will also be room for un-conference topics 18:20:50 <colindixon> #info there is an intent/policy/NB abstraction topic that might get it's own room for most of the time, dlenrow is going to be using a it as a semi-workshop on the topic 18:21:16 <colindixon> #link https://www.opendaylight.org/events/2016-03-13-000000-2016-03-17-000000/open-networking-summit our mini-sumit at ONS has a CFP closes Friday 2/5 18:22:13 <colindixon> #link https://www.opendaylight.org/events/2016-04-25-000000-2016-04-29-000000/openstack-summit is in April in Austin, the CFP closed on Monday 2/1 18:22:20 <colindixon> #info see other events on the events page above 18:22:54 <colindixon> #topic boron 18:23:07 <colindixon> #Info anipbu beyond jdk8 stuff above, we're good 18:23:10 <colindixon> #topic beryllium 18:23:45 <colindixon> #Info anipbu says there was a recent weather item about extra routes not being provided in neutron, the patch affected OVSDB, VPNservice, and GBP and it broke autorelease 18:24:25 <colindixon> #info this issue must be resolved in order to avoid blocking RC2 tonight at UTC 23:59:59 18:24:56 <colindixon> #info anipbu say that the affected projects have merged their patches and it should mean autorelease will build successfully 18:25:22 <colindixon> #info there is a concern about VTN being aware of and/or affected by this as well, anipbu has reached 18:26:02 <jamoluhrsen> RC1 csit status https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=879332351 18:26:06 <colindixon> #link https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=1798258463 issues with RC 1 18:26:36 <colindixon> #info we're tracking the issues and trying to fix them by RC2 which is the final test buidl 18:26:57 <colindixon> #Info RC3 will be the actual release candidate and will be released the week after unless there are no issues 18:27:11 <anipbu> #link https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=45904332 <-- Sign up for Release Review 18:28:22 <colindixon> #info colindixon says it would be really good if we think we fixed all the issues we saw in RC1 in RC2 before we cut it, worst-case we can cut an RC2.1 to evaluate that 18:29:18 <colindixon> #info zxiiro notes that autorelease run daily, so we will have RC2.1 even if we dont' call it that 18:29:33 <colindixon> #topic stable/lithium 18:29:36 <colindixon> #Info nothing this week 18:29:44 <colindixon> #topic system integration and test 18:30:29 <colindixon> #info jamoluhrsen says that there are 23 projects that don't have system test waivers yet arent' reporting system test results 18:31:30 <colindixon> #action jamoluhrsen to produce a list of which projects do not have system tests but promised to do so, so that it can be understood for future tasks, e.g., graduation reviews 18:31:47 <colindixon> #action anipbu to remind people that Lithium-SR4 build is soon (with the actual date) 18:32:09 <colindixon> #topic infrastructure 18:32:34 <colindixon> #info zxiiro says not much to report, the port issues with rackspace have seemed to go away now that they reap broken ports every 4 hours 18:32:53 <colindixon> #topic Tomas Cere as a commiter on NETCONF 18:33:04 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-February/004622.html request to the TSC 18:33:19 <colindixon> #link https://lists.opendaylight.org/pipermail/netconf-dev/2016-February/000236.html two +1s which is a majority 18:33:32 <colindixon> #link https://git.opendaylight.org/gerrit/#/q/owner:%22Tomas+Cere+%253Ctcere%2540cisco.com%253E%22+project:netconf patches 18:35:10 <colindixon> #startvote shall the TSC approve Tomas Cere on the NETCONF project? -1, 0, +1 18:35:10 <odl_meetbot> Begin voting on: shall the TSC approve Tomas Cere on the NETCONF project? Valid vote options are -1, 0, +1. 18:35:10 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts. 18:35:18 <rovarga> #vote +1 18:35:20 <abhijitkumbhare> #vote +1 18:35:21 <dfarrell07> #vote +1 18:35:23 <ttkacik> #vote +1 18:35:24 <colindixon> #vote +1 18:35:38 <mohnish_> #vote +1 18:35:40 <colindixon> mohnish_, LuisGomez 18:35:40 <LuisGomez> #vote +1 18:35:43 <colindixon> #endvote 18:35:43 <odl_meetbot> Voted on "shall the TSC approve Tomas Cere on the NETCONF project?" Results are 18:35:43 <odl_meetbot> +1 (7): rovarga, LuisGomez, dfarrell07, colindixon, ttkacik, mohnish_, abhijitkumbhare 18:36:01 <colindixon> #agree Tomas Cere is now a comitter on NETCONF 18:36:16 <colindixon> #topic VTN graduation review 18:36:32 <colindixon> #link https://wiki.opendaylight.org/view/VTN:Graduation_Review the graduation review proposal 18:36:49 <colindixon> #link https://lists.opendaylight.org/pipermail/project-proposals/2015-December/000388.html requested on 12/29/2016 18:37:55 <colindixon> #Info VTN has been part of ODL since Hydrogen really the beginning 18:38:34 <dfarrell07> VTN system tests look good 18:38:44 <colindixon> #info colindixon can confirm that the docuemntation for VTN is consistently the most up-to-date and thorough 18:38:48 <dfarrell07> #info LuisGomez and dfarrell07 say VTN system tests are good 18:38:52 <colindixon> dfarrell07: thanks! 18:39:12 <rovarga> #info VTN tests overall rock, they caught a very elusive YT bug ;-) 18:40:26 <colindixon> #info colindixon notes that they are good a hitting deadlines (even removing their dependency on the MD-SAL) and communicate well in advance if they might miss one 18:40:40 <colindixon> #info hideyuki reminds colindixon that VTN is used by NIC and so is not a leaf project 18:41:24 <colindixon> #info rovarga notes that he doesn't think we have another project of this scope with this carefully controlled and understood sonar issues 18:41:43 <colindixon> #startvote shall the TSC graduate the VTN being mature? -1, 0, +1 18:41:43 <odl_meetbot> Begin voting on: shall the TSC graduate the VTN being mature? Valid vote options are -1, 0, +1. 18:41:43 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts. 18:41:48 <ttkacik> #vote +1 18:41:49 <dfarrell07> #vote +1 18:41:50 <rovarga> #vote +1 18:41:51 <LuisGomez> #vote +1 18:41:53 <colindixon> #vote +1 18:41:57 <abhijitkumbhare> #vote +1 18:42:04 <mohnish_> #vote +1 18:42:08 <colindixon> #endvote 18:42:08 <odl_meetbot> Voted on "shall the TSC graduate the VTN being mature?" Results are 18:42:08 <odl_meetbot> +1 (7): rovarga, LuisGomez, dfarrell07, colindixon, ttkacik, abhijitkumbhare, mohnish_ 18:42:19 <colindixon> #agree the VTN project is now mature 18:42:20 <dfarrell07> congrats VTN! 18:42:21 <hideyuki> Thank you all! 18:42:27 <LuisGomez> congrats vtn 18:42:31 <anipbu> Congrats VTN! 18:42:32 <mohnish_> congrats to VTN 18:42:41 <colindixon> #action hideyuki to update the relevant wiki pages (project facts temple and the graduation review template) 18:44:02 <colindixon> #action colindixon to make sure we have an accurate list of oustanding project proposals 18:44:56 <colindixon> #topic beryllium release mechanics 18:45:29 <colindixon> #info we will vote go/no-go on 2/18, the PR launch with LF marketing will be on Monday, 2/22 18:45:39 <colindixon> #info assuming that things go well on 1/18 18:46:10 <colindixon> #topic Boron Planning Summary 18:46:17 <colindixon> #info rovarga says he's not sure we have a large scale update 18:46:45 <colindixon> #info the discussion is looking at both shortening the development cycle and trying to decouple development between the different offsets to reduce transient failures 18:46:57 <colindixon> #link https://lists.opendaylight.org/pipermail/discuss/2016-February/006140.html most recent mailing list thread 18:47:05 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tws/opendaylight-meeting-tws.2016-01-11-18.27.html TWS meeting 1 18:47:12 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tws/opendaylight-meeting-tws.2016-01-25-18.00.html TWS meeting 2 18:47:20 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tws/opendaylight-meeting-tws.2016-02-01-18.02.html TWS meeting 3 18:48:12 <colindixon> #info rovarga says that there seems to be some consensus that 6 months is too long and causing us some issues with too much time to drift apart before syncing 18:48:42 <colindixon> #info rovarga says the current theory would be having harder syncs every 2-4 months to try ot reduce drift while still preventing transient breakages 18:49:03 <colindixon> #info rovarga says he thinks there's still work to be done to figure out if we could really adopt this in Boron 18:49:46 <rovarga> #info Boron, Carbon, Nitrogen are the next three 18:49:51 <colindixon> rovarga: thanks 18:50:08 <colindixon> #link https://wiki.opendaylight.org/view/New_workflow_proposal new workflow from skitt and rovarga 18:50:18 <colindixon> #link https://wiki.opendaylight.org/view/Semantic_Versioning semantic versioning which goes along with it 18:50:39 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-January/004565.html Advisory Requests for Boron 18:51:07 <colindixon> #info rovarga says we don't have a target date for the Boron release 18:51:20 <colindixon> #info abhijitkumbhare says shouldn't we try to hit before the OpenDaylight summit on 9/27 18:51:45 <colindixon> #info phrobb- says we targeted the summit to match a likely Boron release, but that it's not required 18:51:52 <colindixon> #info rovarga says we should pick that target and work from there 18:52:26 <colindixon> #action colindixon to draft up a Boron release plan that looks like Beryllium and hits before the ODL Summit just in case 18:52:51 <dfarrell07> colindixon: I think that's a good idea^^ 18:53:13 <abhijitkumbhare> +1 about good idea ^^ 18:53:27 <rovarga> #action rovarga to follow up with a counter-proposal with the new workflow ;-) 18:53:49 <dfarrell07> #info The way the current fast release proposal works, it would be an 2 months + 2 months * offset, so we may have time to bail out if a new plan seems to be failing 18:54:03 <dfarrell07> #undo 18:54:07 <dfarrell07> #info The way the current fast release proposal works, it would be an 2 months + 2 months * offset, so we may have time to bail out if a new plan seems to be failing, says colindixon 18:54:11 <colindixon> #chair dfarrell07 18:54:11 <odl_meetbot> Current chairs: anipbu colindixon dfarrell07 phrobb- 18:55:04 <colindixon> #topic cookies 18:55:07 <colindixon> #endmeeting