========================== #opendaylight-meeting: tsc ========================== Meeting started by phrobb1 at 17:00:00 UTC. The full logs are available at http://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-04-09-17.00.log.html . Meeting summary --------------- * Roll Call - TSC Members please #info in (phrobb1, 17:00:36) * regXboi (regXboi, 17:00:44) * LuisGomez (LuisGomez, 17:01:15) * edwarnicke (edwarnicke, 17:01:16) * colindixon (colindixon, 17:01:37) * LINK: https://wiki.opendaylight.org/view/TSC:Main#Agenda the agenda in it’s usual place (colindixon, 17:02:04) * LINK: https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-04-02-17.00.html last week’s minutes for action items (colindixon, 17:02:18) * chris wright (cdub, 17:02:43) * Youcef Laribi (Youcef, 17:02:54) * ACTION: LuisGomez to start drafting a list of qualifiers for an issue for being a blocker to an SR - edwarnicke to assist (colindixon, 17:03:38) * Eric Multanen (for Uri) (snackewm, 17:03:51) * mohnish anumala (mohnish, 17:03:54) * ACTION: colindixon to e-mail regXboi, Wojciech. edwarnicke, and Mahesh t talk about AAA keystone federation and if we need to worry about anything (colindixon, 17:04:46) * abhijitkumbhare for Chris Price (abhijitkumbhare, 17:05:01) * ACTION: LuisGomez to start a thread about how to unblock integration testing until patches are merged (colindixon, 17:06:06) * dlenrow (dlenrow, 17:07:29) * there’s a hackfest with 91 people registered for next week (colindixon, 17:08:10) * we’ll meet on wednesday morning on a few high-level topics, then unconference the rest (colindixon, 17:09:05) * high-level topics include licensing, export control, etc. while we have people in the room (colindixon, 17:09:32) * ACTION: everyone that cares do the gpg keysigning stuff here: https://lists.opendaylight.org/pipermail/tsc/2015-April/002841.html (colindixon, 17:10:08) * tykeal points out that it’s odd to have 2 year expirations, either infinite or 10 years is more common (colindixon, 17:11:34) * hackfest starts at 9a (colindixon, 17:12:22) * stable/helium (colindixon, 17:12:52) * zxiiro says we got the version bump done for SR3 and so we’re ostensibly chugging to SR4 (colindixon, 17:13:16) * lithium update (colindixon, 17:13:21) * dlenrow says he hopes to get existing comitters to move things along with perisstence (colindixon, 17:14:36) * ACTION: phrobb1 to e-mail jan about SXP (colindixon, 17:14:51) * LINK: https://wiki.opendaylight.org/view/Weather the weather page for Lithium (colindixon, 17:15:06) * LINK: https://wiki.opendaylight.org/view/Weather#Karaf_3.0.3_Upgrade we will be moveing to Karaf 3.0.3 next week, there’s extensive information about ho to test it and recoring known issues (colindixon, 17:15:48) * on previous topic: we have some movement with current SXP committers, so it looks like option #1 will work (rovarga, 17:16:37) * ACTION: regXboi and/or edwarnicke will post things about moxy to the weather page and/or add it to release notes with a workaround (colindixon, 17:18:17) * system integration and test (colindixon, 17:20:56) * nothing this week, other than that we are starting to work on S3P tests and integration folks plan to use the whole second day to build tests (colindixon, 17:21:33) * infrastructure (colindixon, 17:21:44) * ACTION: phrobb1 to send mail to release encouraging people to send keys (colindixon, 17:22:45) * beryllium planning (colindixon, 17:23:08) * regXboi asks should we discuss isotope option for release planning? (phrobb1, 17:24:48) * the high order bit of the release discussion is that the target has been two major releases per year and some are asking if we should be aiming at one major and additional minor (regXboi, 17:26:35) * abhijitkumbhare and LuisGomez say they like the element/isotope appraoch with one major and one minor release per year (colindixon, 17:28:30) * rovarga says he likes it but he worries that it might slow down feature development (colindixon, 17:30:06) * cdub notes that doing fewer major releases per year is the wrong direction. Releasing more often is the right direction (phrobb1, 17:30:30) * cdub notes that we don’t seem to have a goal for what we’re focusing on in designg releases which is why the discussion is somewhat less productive than we might hope (colindixon, 17:33:36) * cdub says that he’d like to see more, lighter-weight releases per year (colindixon, 17:33:52) * cdub notes that doing 1 major release per year means only one per year we can manage architectural (stable/scale/performance/etc) issues (phrobb1, 17:34:54) * LuisGomez says that in his opinion we do need to focus on S3P, so that’s one clear goal (colindixon, 17:35:04) * rovarga advocates for frequent (or continuous) releases (colindixon, 17:37:50) * there is discussion about how you do focus on things, if you give focus teeth and stop people from working on other things, you risk losing people (colindixon, 17:38:59) * colindixon says nobody has suggested stopping people from working on things, but to enoucage people to work on some areas with non-zero resources (colindixon, 17:39:54) * Discussion ensues on the need to make the tooling and process more agile and geared toward continuous release if we are to explore more frequent light-weight releases (phrobb1, 17:39:55) * regXboi and edwarnicke note that when we declared a focus on Neutron, not as many resources came out as we’d hoped for (colindixon, 17:40:22) * mohnish says that part of Beryllium should look at maturity of projects (colindixon, 17:44:02) * colindixon notes that in the absense of more information suggests Beryllium should target a time frame similar or less than Lithium and focus on S3P to the extent the community is comfortable on focusing on that. (phrobb1, 17:44:45) * AGREED: phrobb1 to draft a Beyrillum release plan based on Lithium that is shorter and includes a focus on S3P and use cases (colindixon, 17:48:02) * ACTION: phrobb1 to draft a Beyrillum release plan based on Lithium that is shorter and includes a focus on S3P and use cases (phrobb1, 17:49:01) * AGREED: phrobb1 to draft a Beyrillum release plan based on Lithium that is shorter and includes a focus on S3P and use cases (dfarrell07, 17:49:09) * Discussion about lower-risk ways to learn about/try cont release (dfarrell07, 17:50:51) * colindixon notes what was requested was identification of resource needs to address requests from the board. Can we identify resources needs now (low hanging fruit) for improving S3P in integration & testing (phrobb1, 17:56:27) * LINK: https://bugs.opendaylight.org/show_bug.cgi?id=1395 (dfarrell07, 18:00:07) * VOTE: Voted on "shall the TSC send the following message to the board: https://lists.opendaylight.org/pipermail/tsc/2015-April/002869.html?" Results are, +1: 8 (phrobb1, 18:01:59) * cookies (colindixon, 18:02:51) Meeting ended at 18:02:52 UTC. Action items, by person ----------------------- * colindixon * colindixon to e-mail regXboi, Wojciech. edwarnicke, and Mahesh t talk about AAA keystone federation and if we need to worry about anything * edwarnicke * LuisGomez to start drafting a list of qualifiers for an issue for being a blocker to an SR - edwarnicke to assist * colindixon to e-mail regXboi, Wojciech. edwarnicke, and Mahesh t talk about AAA keystone federation and if we need to worry about anything * regXboi and/or edwarnicke will post things about moxy to the weather page and/or add it to release notes with a workaround * LuisGomez * LuisGomez to start drafting a list of qualifiers for an issue for being a blocker to an SR - edwarnicke to assist * LuisGomez to start a thread about how to unblock integration testing until patches are merged * phrobb1 * phrobb1 to e-mail jan about SXP * phrobb1 to send mail to release encouraging people to send keys * phrobb1 to draft a Beyrillum release plan based on Lithium that is shorter and includes a focus on S3P and use cases * regXboi * colindixon to e-mail regXboi, Wojciech. edwarnicke, and Mahesh t talk about AAA keystone federation and if we need to worry about anything * regXboi and/or edwarnicke will post things about moxy to the weather page and/or add it to release notes with a workaround People present (lines said) --------------------------- * colindixon (54) * dfarrell07 (17) * phrobb1 (16) * odl_meetbot (12) * regXboi (10) * cdub (10) * snoble (7) * rovarga (4) * dneary (3) * tykeal (3) * edwarnicke (3) * mohnish (3) * abhijitkumbhare (3) * dlenrow (2) * LuisGomez (2) * snackewm (2) * zxiiro (1) * Youcef (1) * tbachman (0) Generated by `MeetBot`_ 0.1.4