17:31:24 #startmeeting tsc 17:31:24 Meeting started Mon Nov 10 17:31:24 2014 UTC. The chair is phrobb. Information about MeetBot at http://ci.openstack.org/meetbot.html. 17:31:24 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:31:24 The meeting name has been set to 'tsc' 17:31:31 phrobb: thx 17:31:39 #info regXboi (irc only) 17:31:43 #topic Roll Call - TSC members please #info in 17:31:47 #info dlenrow 17:31:52 * regXboi jumps the gun 17:32:09 #info colindixon 17:32:19 #chair tbachman colindixon edwarnicke_ 17:32:19 Current chairs: colindixon edwarnicke_ phrobb tbachman 17:32:46 https://meetings.webex.com/collabs/#/meetings/detail?uuid=MEME176XJHU3O6MQ2WIS54FBIO-9VIB&rnd=320201.28932 17:33:00 ^^^^ that’s the WebEx URL for those who need it 17:33:11 * gzhao will dial in webex soon 17:33:24 #info jmedved 17:33:27 #info edwarnicke 17:33:34 #info Luis Gomez 17:33:56 * gzhao password expired 17:34:56 mohnish: can you #info in? 17:35:20 #link https://lists.opendaylight.org/pipermail/tsc/2014-November/002096.html an e-mail I sent ~30 minutes ago going trhough what we need to do here 17:35:23 #info mohnish 17:35:47 #topic helium SU1 Release 17:35:48 #topic Helium SU1 Release 17:36:05 #link https://lists.opendaylight.org/pipermail/tsc/2014-November/002096.html an e-mail I sent ~30 minutes ago going trhough what we need to do here 17:36:38 #info since release artifacts were cut, we’ve had no other critical bugs come up, LuisGomez ran all the regression tests with success 17:37:00 #link https://lists.opendaylight.org/pipermail/integration-dev/2014-November/002021.html email indicating to push this to the next SR 17:37:16 what is "this"? 17:37:29 good call 17:37:30 #undo 17:37:30 Removing item from minutes: 17:37:54 #link https://lists.opendaylight.org/pipermail/integration-dev/2014-November/002021.html email indicating to push fix for clustering to the next SR 17:38:02 tbachman: thank you :) 17:38:18 #link https://nexus.opendaylight.org/content/groups/staging/org/opendaylight/integration/distribution-karaf/0.2.1-Helium-SR1/ link to download release artifacts from nexus 17:38:45 #link https://docs.google.com/spreadsheets/d/1TRYposNDFPaKcySlvwkOXvfR6Anx2EFujlIjoTthhRY/edit#gid=1109333662 Spreadsheet with critical bugs 17:39:26 do we need to update status on those defects before voting? 17:39:27 #info we 17:39:29 ugh 17:39:30 #undo 17:39:30 Removing item from minutes: 17:39:43 #startvote Shall the TSC approve the official release of Helium SR-1? -1, 0, +1 17:39:43 Begin voting on: Shall the TSC approve the official release of Helium SR-1? Valid vote options are -1, 0, +1. 17:39:43 Vote using '#vote OPTION'. Only your last vote counts. 17:39:48 #vote +1 17:39:52 #vote +1 17:39:52 #vote +1 17:39:54 #vote +1 17:39:55 #vote +1 17:39:56 #vote +1 17:40:04 #vote +1 17:40:15 * regXboi notes - that should cover it... 17:40:26 #endvote 17:40:26 Voted on "Shall the TSC approve the official release of Helium SR-1?" Results are 17:40:26 +1 (7): dlenrow, jmedved, regXboi, LuisGomez, edwarnicke, mohnish, colindixon 17:40:33 Whoopee! 17:40:39 * tbachman claps loudly 17:40:48 * gzhao claps 17:40:49 congrats! 17:40:52 +1 to tbachman clap 17:41:02 Awesome, congrats to everybody! 17:41:04 Well done guys 17:41:07 #agreed TSC approves the on-time shipment of Helium SR-1 17:41:19 #topic Lithium Release Plan 17:41:19 * tykeal happens to look at this IRC channel when the vote is happening. Does anyone happen to know the staging repo ID that relates to this? 17:42:14 https://nexus.opendaylight.org/content/groups/staging/org/opendaylight/integration/distribution-karaf/0.2.1-Helium-SR1/ 17:42:33 that's not the repo ID that's a meta group that merges _all_ the staging repos for public view 17:42:45 tykeal, we're working on it 17:42:46 at present it is made up of 4 staging repos 17:42:54 #action gzhao or edwarnicke will provide tykeal with th repo ID 17:43:01 thank you 17:43:17 #topic Lithium Simultaneous Release Discussion 17:43:28 sorry tbachman 17:43:28 #info There have been 2 edits of substance since the Li release plan was reviewed at last Thursday’s TSC 17:43:33 phrobb: np! :) 17:43:45 #link https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Lithium_Project_Integration_Requirements integration requirements 17:45:10 #info System test is encouraged to use robot, but if projects want to use something else they can (i.e. don’t mandate technology) 17:45:38 #info Also changed to clarify projects vs. integration projects. 17:46:04 #link https://wiki.opendaylight.org/view/CrossProject:Documentation_Group:Lithium_Project_Documentation_Requirements documentation requirements 17:46:41 question: who is providing the release notes for the Helium SR1 release? 17:46:44 #info This has been updated to make it clear that user documentation should be for user-facing features, and not grouped by project (since they don’t care which project a user-facing feature comes from) 17:47:43 #info The main release page has language added to encourage project to talk about cross-project incompatibilities 17:48:52 #info There’s also been a note added to the feature test section along these same lines 17:49:07 question: if integration has a +2 week offset for M3, how can M4 be kept at the current date? 17:50:27 #action gzhao to email release asking for per-project release notes for stable/helium 17:51:03 #info edwarnicke asks if it’s possible for people to report the outcome of the incompatibility conversations 17:51:48 question: Are projects required to report test results and code coverage for non-java code (e.g. C++ code) to Sonar? 17:52:12 * regXboi notes that's two questions on the channel without answers so far :) 17:52:19 #action colindixon to put together pieces for the release 17:52:39 regXboi: parallel processing ;) 17:52:52 regxboi: we’re just providing an answer to the 1st question :-) 17:52:53 just pointing things out 17:53:04 https://wiki.opendaylight.org/view/Simultaneous_Release:DRAFT_Release_Plan_2014_Template 17:53:11 regXboi: not on dates yet 17:53:29 colindixon: we also need the date on the AI 17:53:35 colindixon: I was looking at the dates in the _ckd draft 17:53:50 #link https://wiki.opendaylight.org/view/Simultaneous_Release:DRAFT_Release_Plan_2014_Template Proposed Lithium Release Plan 17:53:53 I’ll report out on Thursday 17:54:48 #info colindixon asks if anyone objects to edwarnicke’s modification to the release plan re: incompatibilities 17:54:57 #info no objectsions were voiced 17:55:33 uh 17:55:37 what modifications? 17:55:53 regXboi: just a sec.... 17:56:06 are we talking about https://wiki.opendaylight.org/view/Simultaneous_Release:DRAFT_Release_Plan_2014_Template#Expected_Incompatibilities_with_Other_Projects 17:56:08 * tbachman hasn’t pulled up the change yet 17:56:18 #link https://gist.github.com/anonymous/89ec1a86dc1c976618e7 possible date options 17:56:43 regXboi: I believe that’s it 17:57:09 ok, that's fine then 17:57:34 #info colindixon would like to hear feedback on which dates provided in the link appeal to folks 17:58:25 colindixon: I still have problems if integration has a +2 week offset to offset 2 for M3 17:58:53 because that puts integration M3 after offset 0 M4 17:59:22 regXboi: I don’t understand why that would matter 17:59:46 regXboi: its *just* for building project-wide system tests 17:59:56 cough cough 18:00:37 * regXboi can just see the possible exceptions of having to change something related to M3 after M4 because of it... if folks are willing to run that risk, I'll shut up 18:02:14 #info LuisGomez says he has no preference from the testing perspective 18:03:23 * regXboi will go on record as saying +1 to Ed's dates 18:05:18 #info colindixon asks edwarnicke if he prefers his original dates or the +2 weeks to M1 18:05:58 #info edwarnicke says he prefers to have weekly RC’s, which was the motivation for his dates 18:06:33 huh? weekly or bi-weekly? 18:06:51 regXboi: My point is that having RCs ever week at the end is better than having them every 2 weeks 18:06:55 regXboi: it appears edwarnicke’s dates weren’t correct (i.e. didn’t reflect that) 18:06:56 regXboi: Its a cadence thing 18:07:07 tbachman caught my point 18:07:08 regXboi: colindixon is fixing this now I think 18:07:10 https://gist.github.com/anonymous/8f5b41c666847a9a3385 18:07:29 #link https://gist.github.com/anonymous/8f5b41c666847a9a3385 updated dates for Lithium Release 18:08:14 #undo 18:08:14 Removing item from minutes: 18:08:20 :) 18:08:33 #link https://gist.github.com/anonymous/8f5b41c666847a9a3385 updated proposed dates for Lithium Release 18:08:49 phrobb: Could we do options #1 and #2 (to vote between two options)? 18:08:58 well, if that's the case, I'd almost rather see M2/RC0 in ed's dates moved out a week so that release falls on 6/25 18:09:43 regXboi: where would you add the wek? 18:09:47 edwarnicke: yup 18:10:31 M2->1/29, M3->2/26, M4->3/26, M5->4/23, RC0->6/4 RC1->6/11 RC2->6/18, Release->6/25 18:10:38 colindixon: ^^ 18:10:55 regXboi: What is the source of your desire to move out the release to 6/25? (not objecting, seeking to object) 18:10:55 seeking to understand 18:11:26 regXboi: how about adding an RC? 18:11:46 * tbachman reminds folks that regXboi has no audio today 18:11:48 I don't want to push into the 7/4 weekend, but I don't see why shorting us a week on M2 is so good an idea 18:12:03 tbachman: we could add an RC if needed 18:12:07 regXboi: I think my dates do *not* short M2 18:12:38 colindixon:separating biweekly from weekly RC cadence is brilliant :) 18:12:54 relative to the others I think it may be - that's all 18:13:41 colindixon: no TWS, so we have the time slot :) 18:15:03 regXboi: Good point about the 7/4 week 18:15:04 #startvote Shall the TSC declare weekly (Option 1) or bi-weekly (Option 2) RC candidates for the Lithium Release? 1, 2 18:15:04 Begin voting on: Shall the TSC declare weekly (Option 1) or bi-weekly (Option 2) RC candidates for the Lithium Release? Valid vote options are 1, 2. 18:15:04 Vote using '#vote OPTION'. Only your last vote counts. 18:15:14 #vote 1 18:15:16 #vote 1 18:15:26 no abstain? 18:15:33 #vote 1 18:15:35 #vote 1 18:15:43 #vote 2 18:15:43 #vote 1 18:15:59 #endvote 18:15:59 Voted on "Shall the TSC declare weekly (Option 1) or bi-weekly (Option 2) RC candidates for the Lithium Release?" Results are 18:15:59 1 (4): dlenrow, LuisGomez, edwarnicke, mohnish 18:15:59 2 (1): colindixon 18:16:41 #startvote Shall the TSC declare the Lithium Release plan to contain 3, or 4 RCs? 3, 4 18:16:41 Begin voting on: Shall the TSC declare the Lithium Release plan to contain 3, or 4 RCs? Valid vote options are 3, 4. 18:16:41 Vote using '#vote OPTION'. Only your last vote counts. 18:16:50 #vote 4 18:16:53 #vote 4 18:16:55 #vote 3 18:16:59 #vote 4 18:17:01 #vote 4 18:17:04 #vote 4 18:17:08 * regXboi prefers to add a fourth if we need it 18:17:14 #endvote 18:17:14 Voted on "Shall the TSC declare the Lithium Release plan to contain 3, or 4 RCs?" Results are 18:17:14 3 (1): regXboi 18:17:14 4 (5): mohnish, LuisGomez, colindixon, dlenrow, jmedved 18:17:31 regXboiI didn't get to vote on that 18:17:49 that was boi: not boil :) 18:18:00 dlenrow: I also had an IRC glitch, but am pleased by the 4 RC result :) 18:18:48 edwarnicke: I meant I didn't get to vote on Ryans variation of language. My poor attempt at humor 18:20:29 #startvote Shall the TSC declare M1 for Lithium starting on 11/21 (Option 1), or on 12/11 which allows approximately 4 weeks between M0 and M1(Option 2)? 1, 2 18:20:29 Begin voting on: Shall the TSC declare M1 for Lithium starting on 11/21 (Option 1), or on 12/11 which allows approximately 4 weeks between M0 and M1(Option 2)? Valid vote options are 1, 2. 18:20:29 Vote using '#vote OPTION'. Only your last vote counts. 18:20:37 #vote 1 18:20:40 #vote 2 18:20:46 #vote 2 18:20:47 #vote 2 18:20:48 #vote 2 18:20:53 #vote 2 18:20:58 #vote 2 18:21:05 #endvote 18:21:05 Voted on "Shall the TSC declare M1 for Lithium starting on 11/21 (Option 1), or on 12/11 which allows approximately 4 weeks between M0 and M1(Option 2)?" Results are 18:21:05 1 (1): colindixon 18:21:05 2 (6): dlenrow, jmedved, regXboi, LuisGomez, edwarnicke, mohnish 18:21:33 are we going to go through each milestone like that? 18:21:41 * regXboi shudders 18:23:16 #info it’s my understanding that this means we weill use the following offset 0 dates M0: 11/11, M1: 12/11, M2: 1/22 M3: 2/1, M4: 3/19, M5: 4/16, RC0: 5/28, RC1: 6/4, RC2: 6/11, RC3: 6/18, Release: 6/25, SR1: 8/13, SR2: 9/24 18:23:37 M3 2/1 or 2/19? 18:23:57 #undo 18:23:57 Removing item from minutes: 18:24:00 #info M0: 11/11, M1: 12/11, M2: 1/22 M3: 2/19, M4: 3/19, M5: 4/16, RC0: 5/28, RC1: 6/4, RC2: 6/11, RC3: 6/18, Release: 6/25, SR1: 8/13, SR2: 9/24 18:24:03 #undo 18:24:03 Removing item from minutes: 18:24:20 #info it’s my understanding that this means we weill use the following offset 0 dates M0: 11/11, M1: 12/11, M2: 1/22 M3: 2/19, M4: 3/19, M5: 4/16, RC0: 5/28, RC1: 6/4, RC2: 6/11, RC3: 6/18, Release: 6/25, SR1: 8/13, SR2: 9/24 18:24:59 #info I withdraw my previous suggestion of M2 at 1/29 18:24:59 colindixon: thx for doing those dates 18:25:14 #startvote Shall the TSC approve the Lithium Release Plan as documented on the wiki as DRAFT_Lithium_Release_Plan_ckd with the date-modification indicated above? -1, 0, +1 18:25:14 Begin voting on: Shall the TSC approve the Lithium Release Plan as documented on the wiki as DRAFT_Lithium_Release_Plan_ckd with the date-modification indicated above? Valid vote options are -1, 0, +1. 18:25:14 Vote using '#vote OPTION'. Only your last vote counts. 18:25:19 #vote +1 18:25:33 #vote +1 18:25:36 #vote +1 18:25:36 #vote +1 18:25:36 #vote +1 18:25:36 #vote +1 18:25:37 #vote +1 18:25:49 * regXboi notes "and we have liftoff..." 18:25:51 #endvote 18:25:51 Voted on "Shall the TSC approve the Lithium Release Plan as documented on the wiki as DRAFT_Lithium_Release_Plan_ckd with the date-modification indicated above?" Results are 18:25:51 +1 (7): dlenrow, jmedved, regXboi, LuisGomez, edwarnicke, mohnish, colindixon 18:25:54 * tbachman hands colindixon a celebratory vBeer 18:26:08 #action colindixon to make the date adjustments to the Li Release Plan 18:26:28 * edwarnicke considers getting colindixon a celebratory pBear 18:26:31 pBeer 18:26:38 #action colindixon to remove the “Draft” indications from the documents that say “Draft” 18:26:42 * edwarnicke tries not to get Bears for his friends 18:26:48 lol! 18:27:02 * regXboi is still looking for the super-cow 18:27:10 colindixon: no TWS today 18:27:19 #endmeeting