17:01:03 #startmeeting tsc 17:01:03 Meeting started Thu Sep 11 17:01:03 2014 UTC. The chair is phrobb. Information about MeetBot at http://ci.openstack.org/meetbot.html. 17:01:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:01:03 The meeting name has been set to 'tsc' 17:01:13 #info Chris Wright 17:01:38 #chair colindixon cdub regXboi 17:01:38 Current chairs: cdub colindixon phrobb regXboi 17:01:46 #topic roll call and agenda 17:01:49 #topic Roll Call 17:01:55 sorry 17:02:00 #info TSC members please #info in 17:02:00 #info lenrow 17:02:02 #info Ivan Wood 17:02:28 On my way to audio... 17:02:48 We need to kill the entry tone for our WebEx's :) "dee doop" "dee doop" "dee doop" "dee doop" "dee doop" "dee doop" 17:03:01 #info regXboi 17:03:24 #info EdM_ 17:03:31 #info edwarnicke 17:04:32 #info Kent Watsen 17:04:35 #link https://wiki.opendaylight.org/view/TSC:Main#Meeting_Agenda 17:05:09 #info warning that we may not get to the Creation Review for today 17:05:38 #info cdub running meeting for dmm who may be late 17:05:44 #topic Updates 17:06:09 #info discovery team is on standby for the creation review - no worries if it is not accomplished today 17:06:09 #info Phil reporting on events update - at 120 people for 9/29 Lithium meetup 17:06:22 can people share my screen? 17:06:25 see 17:06:29 #chair tbachman 17:06:29 Current chairs: cdub colindixon phrobb regXboi tbachman 17:06:30 yes 17:06:40 regXboi: /) 17:06:44 ;? 17:06:45 colindixon: yes. I can see your screen. 17:06:47 lol 17:06:48 can’t type 17:06:53 #info we need people to RSVP to get accurate counts for the design forum 17:06:56 #info upcoming events includes hackfest in dusseldorf in October 17:07:12 #info as well as openstack summit in paris in November 17:07:58 #info Phil reporting on branding - it is still progressing through marketing with no update for today 17:08:03 #topic elections 17:08:12 #info please vote, it closes soon (e-mails were sent) 17:08:15 #info Phil reporting on at-large elections - deadline is Monday - if you haven't voted, please do so 17:08:22 #info abhijitkumbhare proxy for Chris Price (my laptop had crashed - so did not info in earlier 17:08:24 #topic documentation update 17:08:31 #undo 17:08:31 Removing item from minutes: 17:08:39 #topic system integration/testing update 17:08:41 * colindixon steps back to allow regXboi to have fun 17:08:58 #info the Helium RC0 candidate is under test 17:09:09 * regXboi asks colindixon to help catch stuff :) 17:09:57 #info there are issues that have been found that have been shared in email - these may be covered during Helium release status update 17:10:10 #topic Documentation update 17:10:41 #info Manny reports that things are going to be tight for the core docs, but it looks like they will be published by 9/29 17:11:03 #info open items remaining are CLI commnads for the controller and procedures for integrating the controller with other projects 17:11:52 #info cdub worries that this is a definite risk point 17:12:07 #info cdub notes we are a ways from the deadline, but what contingency plans do we have to complete documentation? 17:12:56 #info reply from Manny is that the scope has been pared way back but the documentation will still be "best-effort" given the new authors, tool set, etc. 17:13:54 #topic Helium release status 17:14:53 colindixon: can you #link the URI? 17:15:00 yeah two sec 17:15:14 * regXboi doesn't have it where it is easily copy/pasted :( 17:15:20 #link https://docs.google.com/spreadsheets/d/1TRYposNDFPaKcySlvwkOXvfR6Anx2EFujlIjoTthhRY/edit 17:15:38 #info above link is current Helium release status (thanks Colin) 17:16:18 #info on the karaf tab, everyone is green or pending review except Defense4All (not started) and SDNi (work in progress) 17:16:51 #info on the General Tab, most are yellow (one red) 17:17:24 #info an existing issue is that the project contacts are not clear on what each of the milestones mean 17:17:47 gzhao: so, we have an item later to define RC milestones at least 17:18:35 #info and therefore the milestone status reported may not be 100% accurate 17:19:53 #info cdub points out that it’s probably an (odd) good sign that some projects are dropping out when they realize that they either won’t make it or aren’t a good fit 17:19:59 #topic committer promotions 17:20:10 Thomas Bachman to committer on Group Based Policy 17:20:13 #link https://lists.opendaylight.org/pipermail/tsc/2014-September/001631.html 17:20:30 #link https://docs.google.com/document/d/10Q_HV6qh52Pay_IQNv6EoJ0F6Z8M8nNrW0RZ4RNtRu0/edit 17:20:40 #link https://lists.opendaylight.org/pipermail/tsc/2014-September/001625.html 17:20:45 regXboi: thanks 17:20:50 cdub: no worries 17:21:21 #info alagalah_ says that tbachman is #2 in code contributions on GBP 17:21:37 #info alagalah_ also notes that he’s also more than willing to help in the community pretty much everywhere 17:21:40 +1 to that last one 17:21:44 +10 to it actually 17:21:48 yes 17:21:50 :) 17:21:54 +100 to the helpful to community :) 17:21:54 #startvote Shall the TSC promote Thomas Bachman to committer on the Group Based Policy project? -1, 0, +1 17:21:54 Begin voting on: Shall the TSC promote Thomas Bachman to committer on the Group Based Policy project? Valid vote options are -1, 0, +1. 17:21:54 Vote using '#vote OPTION'. Only your last vote counts. 17:21:59 #vote +1 17:22:02 #vote +1 17:22:03 #vote +1 17:22:05 #vote +1 17:22:06 #vote +1 17:22:07 #vote +1 17:22:10 colindixon: tbachman is helping two projects moving to Karaf 17:22:21 #vote +1 17:22:26 #endvote 17:22:26 Voted on "Shall the TSC promote Thomas Bachman to committer on the Group Based Policy project?" Results are 17:22:26 +1 (7): dlenrow, regXboi, edwarnicke, cdub, kwatsen, abhijitkumbhare, IvanWood 17:22:34 thanks folks! :) 17:22:37 #agreed Thomas Bachman to committer on the Group Based Policy project 17:22:37 #info gzhao notes that tbachman has also helped moving projects to Karaf in huge ways 17:22:39 Congrats BTO tbachman 17:22:41 congrats! 17:22:43 tbachman: good job 17:22:44 (Bachman Turner Overdrive) 17:22:45 very well deserved 17:22:51 tbachman: congratulations! :) 17:22:56 ;) 17:22:58 regXboi: ;) 17:22:59 lol 17:23:03 * tbachman picks up pen 17:23:19 #topic Helium Issues - Release Vehicles 17:23:27 #undo 17:23:27 Removing item from minutes: 17:23:30 regXboi: pick again ;) 17:24:48 #topic time and location for RC1 cutting 17:25:45 #info the issue is that we would like clarity about when your patches have to be in (and on what branch) in order to be part of the RC1 cutting 17:26:49 #info Madhu notes time/date of RC1 is dependent on Release Vehicles 17:27:28 #info colindixon notes this discussion is just pick a time of day and a location (branch) where to cut from 17:28:12 #info edwarnicke asks that we determine time of day first: 17:29:25 #info phrobb proposes midnight UTC which is 5p pacific 17:29:57 #agreed midnight UTC for time of day to cut RC1 17:31:25 +maxint 17:31:48 #link http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140916T00 this is the (assuming it stays 9/15) for those who want help converting 17:33:13 #info the section question on the table is when do people cut over to helium/stable branches and when does autorelease pull from that instead of master 17:34:00 #info edwarnicke notes that we have a note in the release plan that says projects *must* create a helium/stable branch on/before 9/29 when we do our release 17:35:24 #info abhijitkumbhare points out that really, the only reason you would need a helium/stable branch is to work on lithium, so maybe we can push this off unless people need that 17:36:00 #info rovarga says that actually the ability to have a branch where you can keep relatively few patches right now so that people can target their reviews to those targetted at helium would help even without that 17:36:37 time check 17:36:44 heh, was just about to say same 17:36:49 if we can punt for a week, we should 17:36:54 * tbachman notes that this isn’t the ‘hard’ one 17:37:42 #info regXboi notes that because our relaese plan said projects don’t have to do release/helium until the last second, so our hands may be tied 17:37:55 people don’t watch IRC while they talk 17:38:13 colindixon: I saw :) 17:38:32 colindixon: my info point should be slightly different: abhijitkumbhare points out that really, the only reason you would need a helium/stable branch is to work on lithium, so do we know are any projects working right now toward Lithium? 17:39:08 #info cdub proposes RC1 cut from master, and stick with RCs coming from master through Helium 17:39:13 #info above, abhijitkumbhare actually said “the only reason you would need a helium/stable branch is to work on lithium, so do we know are any projects working right now toward Lithium?” 17:39:31 #agreed we will still cut from master for RC1 17:39:35 #info, edwarnicke notes that one project has a "development" branch and asks that they don't have to move 17:39:55 #und 17:39:57 #undo 17:39:57 Removing item from minutes: 17:39:59 #undo 17:39:59 Removing item from minutes: 17:40:09 #info edwarnicke notes that one project has a "development" branch and asks that they don't have to move 17:40:58 we will cut from the same branches for RC1 as we did for RC0 (mostly master, but some projects may be on other branches as noted above) 17:41:26 and 9/29 is the date that stable/helium must be cut 17:41:44 s/RC1/RC1,RC2/ 17:42:02 #startvote we will cut from the same branches for RC1& RC2 as we did for RC0 (mostly master, but some projects may be on other branches as noted above)? -1, 0, +1 17:42:02 Begin voting on: we will cut from the same branches for RC1& RC2 as we did for RC0 (mostly master, but some projects may be on other branches as noted above)? Valid vote options are -1, 0, +1. 17:42:02 Vote using '#vote OPTION'. Only your last vote counts. 17:42:29 #vote +1 17:42:32 #vote +1 17:42:38 #vote +1 17:43:11 #vote 1 17:43:11 dlenrow: 1 is not a valid option. Valid options are -1, 0, +1. 17:43:12 #vote +1 17:43:15 #vote +1 17:43:35 #vote +1 17:43:54 #endvote 17:43:54 Voted on "we will cut from the same branches for RC1& RC2 as we did for RC0 (mostly master, but some projects may be on other branches as noted above)?" Results are 17:43:54 +1 (6): dlenrow, regXboi, edwarnicke, cdub, abhijitkumbhare, IvanWood 17:43:57 #agreed we will cut from the same branches for RC1& RC2 as we did for RC0 (mostly master, but some projects may be on other branches as noted above) 17:44:10 #agreed (by fiat) 9/29 is the date that stable/helium must be cut 17:44:19 #undo 17:44:19 Removing item from minutes: 17:44:20 #agreed all projects *must* cut helium/stable branches on or before 9/29 (this was agreed on in the past, but reiterated here) 17:44:50 Does this mean that if a bug fix is committed by 9/28 its in Helium 17:44:51 ? 17:44:57 Or is there another date for final bug fixes? 17:45:08 #topic criteria for RC1 17:45:15 #undo 17:45:15 Removing item from minutes: 17:45:15 alagalah_: no, that was code freeze 17:45:17 #topic articulate criteria for RC1 17:45:22 thanks regXboi 17:45:24 colindixon: Bug Fixes ?? 17:45:49 colindixon: What's final date for bug fix commits/merges ? 17:45:54 alagalah_: so this is just saying that people should cut a branch which is the version of their code which is shipping in helium when we ship it 17:46:13 alagalah_: it’s not saying anything about the patches that go to either one 17:46:16 #info phil proposes: 1 Contains all projects (ie all projects have their karaf features submitted to Integration) 17:46:23 alagalah_: that’s an orthogonal concern 17:46:23 colindixon: ack and thx 17:46:27 #info phil propose: 2 All projects are code-frozen (several projects were not code frozen for RC0) 17:46:34 colindixon: one might also say parallel :-P 17:46:40 #info phil proposes: 3 If a project cannot meet these two criteria by RC1 (Monday, Sept 15th), then they will be dropped from the project - and/or if the TSC wishes the project could apply for an exception - giving a reason (like they have no other projects depending on them) and a drop dead date (like Sept 17th) when they will have the two items above complete. 17:46:51 #link https://meetings.opendaylight.org/opendaylight-meeting/2014/helium_pre_rc0_rc1/opendaylight-meeting-helium_pre_rc0_rc1.2014-09-10-15.30.html 17:47:59 #info request of what projects don't meet these two criteria 17:48:44 #info answer there are three projects that are not in a state to participate in RC1 and these are leaf projects 17:49:26 #info they are SDNi, Defense4All, plugin2oc 17:49:43 Phil - for the last point of dropping a project: TSC can give them an extension if there are no projects depending on them - shouldn’t this be the other way? Because if we drop a project that other projects depend on - then we may need to drop the dependent projects 17:49:53 #info request for what projects aren't code-frozen 17:50:32 #info as of last week seven weren't code frozen as of M5 but three have dropped out: packetcable, sfc, snmp, vtn 17:50:32 #info we don’t have data for code-frozen today, but from M5: 4 projects that have not dropped out (packetcable, sfc, snmp4sdn, vtn) 17:50:41 #undo 17:50:41 Removing item from minutes: 17:50:43 #undo 17:50:43 Removing item from minutes: 17:50:47 thanks 17:50:48 #info we don’t have data for code-frozen today, but from M5: 4 projects that have not dropped out (packetcable, sfc, snmp4sdn, vtn) 17:51:18 hideyuki: There? 17:51:22 yes 17:51:55 #info hideyuki says that VTN will be code-frozen by RC1 17:53:45 fwiw, this is the closest thing I could find in the TSC minutes: 17:53:47 https://meetings.opendaylight.org/opendaylight-meeting/2014/tsc/opendaylight-meeting-tsc.2014-07-31-16.59.log.html 17:55:04 https://meetings.opendaylight.org/opendaylight-meeting/2014/tsc/opendaylight-meeting-tsc.2014-07-31-16.59.log.html#l-132 (with the specific line) 17:56:39 Phil proposes that projects are “in karaf” and “code frozen” to be in RC1, otherwise the TSC has to push RC1 out or drop those projects 17:56:57 that’s my straw man 17:57:05 #startvote shall the criteria for RC1 is 1) karaf features submitted to integration, and 2) you must be code frozen? -1, 0, +1 17:57:05 Begin voting on: shall the criteria for RC1 is 1) karaf features submitted to integration, and 2) you must be code frozen? Valid vote options are -1, 0, +1. 17:57:05 Vote using '#vote OPTION'. Only your last vote counts. 17:57:31 #undo 17:57:31 Removing item from minutes: 17:58:07 irc://irc.freenode.net:6667/#startvote shall the criteria for RC1 is 1) karaf features successfully merged to integration, and 2) you must be code frozen? -1, 0, +1 17:58:19 phrobb: try again 17:58:27 #startvote shall the criteria for RC1 is 1) karaf features successfully merged to integration, and 2) you must be code frozen? -1, 0, +1 17:58:27 Already voting on 'shall the criteria for RC1 is 1) karaf features submitted to integration, and 2) you must be code frozen' 17:58:37 #endvote 17:58:37 Voted on "shall the criteria for RC1 is 1) karaf features submitted to integration, and 2) you must be code frozen?" Results are 17:58:50 #startvote shall the criteria for RC1 is 1) karaf features successfully merged to integration, and 2) you must be code frozen? -1, 0, +1 17:58:50 Begin voting on: shall the criteria for RC1 is 1) karaf features successfully merged to integration, and 2) you must be code frozen? Valid vote options are -1, 0, +1. 17:58:50 Vote using '#vote OPTION'. Only your last vote counts. 17:58:56 #vote +1 17:58:58 #vote +1 17:58:59 #vote +1 17:59:03 #vote +1 17:59:03 #vote +1 17:59:06 #vote +1 17:59:21 #endvote 17:59:21 Voted on "shall the criteria for RC1 is 1) karaf features successfully merged to integration, and 2) you must be code frozen?" Results are 17:59:21 +1 (6): dlenrow, regXboi, edwarnicke, cdub, abhijitkumbhare, IvanWood 17:59:39 #agreed the criteria for RC1 shall be 1) karaf features successfully merged to integration, and 2) you must be code frozen 17:59:54 #info now what to do about exception versus dropped... 18:00:13 #info cdub proposes being harsh and just saying they are dropped 18:00:18 #info edwarnicke agrees 18:00:20 #info edwarnicke agrees with cdub 18:00:20 #startvote If a project does not meet the criteria for RC1, the project will be dropped from the Helium Release? -1, 0, +1 18:00:20 Begin voting on: If a project does not meet the criteria for RC1, the project will be dropped from the Helium Release? Valid vote options are -1, 0, +1. 18:00:20 Vote using '#vote OPTION'. Only your last vote counts. 18:00:25 * regXboi has heart attack 18:01:00 * edwarnicke casts about for automated defibrillation device 18:01:29 #vote +1 18:01:33 #vote +1 18:01:35 #vote +1 18:01:36 #vote +1 18:02:06 #vote +1 18:02:08 IvanWood, dlenrow , others? 18:02:14 * regXboi considers the chicago way - vote early, vote often? 18:02:35 dlenrow: IvanWood 18:02:43 #vote 0 18:03:41 #endvote 18:03:41 Voted on "If a project does not meet the criteria for RC1, the project will be dropped from the Helium Release?" Results are 18:03:41 0 (1): kwatsen 18:03:41 +1 (5): cdub, edwarnicke, IvanWood, abhijitkumbhare, regXboi 18:03:54 #agreed If a project does not meet the criteria for RC1, the project will be dropped from the Helium Release 18:04:07 #vote +1 18:04:20 Does that help. I'm trying to join another call 18:04:21 dlenrow: thanks, but not necessary 18:04:27 #info the record should show that dlenrow voted in favor on the previous measure 18:04:33 Am I dismissed 18:04:35 ? 18:04:38 dlenrow: yes 18:04:40 #undo 18:04:40 Removing item from minutes: 18:04:45 dlenrow: thanks 18:04:52 #info the record should show that dlenrow voted in favor on the previous measure (although it was not required) 18:05:02 #action for gzhao to let projects know of these gates 18:05:06 see it 18:05:13 #undo 18:05:13 Removing item from minutes: 18:05:49 #action gzhao to (aggressively) follow up with project not meeting the RC1 criteria so that they have the best chance of not being dropped 18:05:59 #endmeeting