========================== #opendaylight-meeting: tsc ========================== Meeting started by colindixon at 16:59:54 UTC. The full logs are available at http://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-05-28-16.59.log.html . Meeting summary --------------- * agenda bashing and roll call (colindixon, 16:59:59) * dlenrow (dlenrow, 17:00:13) * colindixon (colindixon, 17:00:32) * LINK: https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-05-21-16.59.html minutes to previous meeting (tbachman, 17:00:39) * LINK: https://wiki.opendaylight.org/view/TSC:Main#Agenda Agenda for today’s meeting (tbachman, 17:00:55) * edwarnicke (edwarnicke, 17:01:10) * ACTION: colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade (colindixon, 17:01:51) * mohnish anumala (mohnish, 17:02:52) * ACTION: LuisGomez and tykeal and jamoluhrsen to work out getting a patch merged in openstack to view all historical performance data (colindixon, 17:03:06) * LuisGomez (LuisGomez, 17:03:28) * Chris Price (ChrisPriceAB, 17:03:53) * LINK: https://lists.opendaylight.org/pipermail/release/2015-May/002443.html Email from phrobb on Beryllium release plan proposal (tbachman, 17:04:06) * Chris Wright (cdub, 17:04:14) * ACTION: ChrisPriceAB to work with rovarga, jmedved, et. al. to look into leveraging OPNFV infrastructure for performance measurements and (tbachman, 17:04:31) * jmedved (jmedved, 17:05:09) * events (colindixon, 17:05:11) * phrobb says ONS is coming up in a few weeks (tbachman, 17:05:27) * LINK: http://www.opendaylight.org/news/events/ the events page in it’s usually place (colindixon, 17:05:36) * phrobb says they’re looking at shifting some things around for the summit — going to put out an agenda for the developer forum shortly after the Lithium release (tbachman, 17:05:56) * colindixon asks for additional topics (tbachman, 17:06:30) * edwarnicke says he’d like to discuss the IPv6 issues with respect to branch-cutting (tbachman, 17:06:48) * rovarga says he doesn’t see the restconf/netconf and other creation reviews (breakout projects) (tbachman, 17:07:57) * colindixon says he’ll schedule this for next week, given the time frame (tbachman, 17:08:06) * Lithium and stable/helium updates (tbachman, 17:08:19) * colindixon asks zxiiro what the status is of autorelease and branch cutting (tbachman, 17:08:43) * zxiiro says autorelease is failing b/c l2switch is trying to build a distribution that no longer exists (tbachman, 17:09:00) * LINK: https://bugs.opendaylight.org/show_bug.cgi?id=3398 bug against l2switch building old distribution (tbachman, 17:09:24) * edwarnicke says l2switch is trying to build a hydrogen style distribution, but that distribution no longer exists (tbachman, 17:09:42) * colindixon asks if downstream projects should wait to bump their versions (tbachman, 17:11:10) * rovarga says until we perform the bumps, we don’t have visibility into what breakages are present (tbachman, 17:12:07) * rovarga says we shouldn’t be shipping Lithium until the corresponding patch in yangtools is merged (cherry-picked) into stable/lithium (tbachman, 17:13:28) * colindixon asks if downstream projects do bump their versions, will this cause issues using two different versions of yangtools (tbachman, 17:13:52) * edwarnicke says this will definitely cause issues (tbachman, 17:14:01) * colindixon says lithium isn’t blocked on this, but the ability to expose bugs in downstream projects is limited (tbachman, 17:14:36) * edwarnicke says cutting master without version bumps is meaningless (tbachman, 17:15:55) * edwarnicke also highlights that a lot of downstream projects feel pressure to "cut" (alagalah, 17:16:18) * LINK: https://git.opendaylight.org/gerrit/#/c/21268/ <- l2switch stable/lithium should not be blocking autorelease anymore (edwarnicke, 17:17:51) * The view of the TSC at this point is that the stable/lithium branch cutting does not block the ability to cut RC releases (tbachman, 17:17:57) * dbainbri asks if there is (a) no requirement to create stable/lithium and (b) we should not version bump (tbachman, 17:19:08) * colindixon says there is currently no value in cutting stable/lithium unless you bump on master; if you cannot bump all your versions on master, you should not cut stable/litihium b/c you get no value, but does increase complexity (tbachman, 17:19:54) * colindixon says that not bumping master, you have two things publishing artifacts to nexus, with no way of saying which one ‘wins’ (tbachman, 17:20:58) * looking at OFP master, I see ./parent/pom.xml: 0.8.0-SNAPSHOT (rovarga, 17:21:16) * ACTION: zxiiro and gzhao to send email to release asking projects to not cut stable/lithium without version bumping (tbachman, 17:22:47) * ebrjohn says that SFC has already cut stable/lithium and not bumped versions (tbachman, 17:23:04) * colindixon says you technically shouldn’t merge to master w/o the version bump (tbachman, 17:23:18) * edwarnicke says it may be easier for SFC to delete the current stable/lithium branch, and then redo it when you’re ready to version bump (tbachman, 17:23:52) * LINK: https://git.opendaylight.org/gerrit/#/c/20316/ patch from edwarnicke that bumped yangtools version in openflowplugin (tbachman, 17:25:09) * LuisGomez says that integration already did their branch — without the branch, there’s no way they can do their testing (tbachman, 17:25:34) * LINK: https://wiki.opendaylight.org/view/Simultaneous_Release:Lithium_Release_Plan#Project_Dependency_Diagram (colindixon, 17:27:46) * edwarnicke says there are a lot of projects that depend on OVSDB, so it’s probably the next project that needs to cut and bump (tbachman, 17:27:53) * LINK: https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-daily-master/lastFailedBuild/artifact/dependencies.log (zxiiro, 17:28:09) * ACTION: zxiiro and gzhao to work to drive the version bump through projects using the dependency chart as a guide: it seems, like the next targets would be OVSDB and L2 Switch, followed by dlux (colindixon, 17:30:33) * rovarga suggests that we force merge the version bump on master and then deal with the issue later to return the build to normal, edwarnicke sees dragons there (colindixon, 17:32:08) * LINK: https://docs.google.com/spreadsheets/d/1KPpO9LH539Vlcoa4RvLa6PPCdLifi5JD-ihRhlybqeo/edit#gid=676729675 blocking bugs (colindixon, 17:34:21) * LINK: https://wiki.opendaylight.org/view/Weather link to weather map page (tbachman, 17:34:39) * System Integration and Test (tbachman, 17:35:59) * OVS 2.3 is working in CI, yay! (colindixon, 17:36:15) * LuisGomez says they cut stable/lithium yesterday (tbachman, 17:36:43) * LuisGomez says their main issue is that all their triggers are “weird” now, so when something fails, it’s hard to know whether it was from stable/lithium or from master (tbachman, 17:37:22) * the key issue is that cross-project triggers are still intra-branch, e.g., master triggerst master, stable/lithium triggers stable/lithium, but that’s not the reality on the ground at the moment (colindixon, 17:37:44) * ACTION: colindixon to follow up with zxiiro and gzhao about version bumps on friday and monday to see if we need interim solutions (colindixon, 17:40:27) * ACTION: colindixon to add bug 3051 the the blocker list and get robert edit access (colindixon, 17:40:43) * Infrastructure (tbachman, 17:41:00) * tykeal says last night there were issues with slaves not working right — resulting in a huge queue today (tbachman, 17:41:29) * colindixon asks how long until this this resolves itself (tbachman, 17:41:43) * tykeal says maybe by midnight — but hard to know for sure (tbachman, 17:41:54) * rovarga asks if we could expand the support staff so that we could reach peopel for issues 24x7 (colindixon, 17:42:56) * ACTION: colindixon to take the issue of more staff for added hours to board (colindixon, 17:43:24) * LINK: https://lists.opendaylight.org/pipermail/tsc/2015-May/003109.html email from ttkacik about LF infra (tbachman, 17:44:09) * Beryllium Release Planning and Board Requests (tbachman, 17:44:44) * LINK: https://wiki.opendaylight.org/view/Simultaneous_Release:Beryllium_Release_Plan the draft release plan (colindixon, 17:44:52) * colindixon asks people to look over it and comment on mailing lists (tbachman, 17:45:13) * colindixon says there’s also an issue that some of the document may not reflect the project lifecycle changes (tbachman, 17:45:46) * ACTION: colindixon to draft changes to language around project lifecycles (tbachman, 17:45:56) * edwarnicke says he feels very bad about voting on that by next Wednesday, as he’s been heads down in development mode (tbachman, 17:46:29) * Moving to Jira (tbachman, 17:47:34) * LINK: https://lists.opendaylight.org/pipermail/tsc/2015-February/002554.html mailing list thread started here (colindixon, 17:48:07) * rovarga says he’d like to get feedback from the community about using bugzilla vs. Trello vs. other tools (tbachman, 17:48:07) * LINK: https://lists.opendaylight.org/pipermail/tsc/2015-March/002730.html and moved here (colindixon, 17:48:13) * LINK: https://lists.opendaylight.org/pipermail/tsc/2015-May/003106.html before ending here (colindixon, 17:48:21) * alagalah would use JIRA for GBP if ODL got a FOSS license from Atlassian (alagalah, 17:49:26) * rovarga says this discussion has been brought up on the mailing lists 2 or 3 times, and has stalled each time; would like to get closure on this — worth moving to Jira? Too much of a disturbance, etc.? (tbachman, 17:49:37) * rovarga also would like to know how the TSC and PTLs feel about using Jira (tbachman, 17:49:57) * edwarnicke says we can split this into two things: can we switch from bugzilla to jira; the other is: how do we manage migrating from bugzilla to jira (tbachman, 17:50:29) * colindixon says there’s another piece — running and operating jira (tbachman, 17:50:47) * colindixon says there’s a cost to migrate from bugzilla to jira, and an operational cost for running jira (tbachman, 17:51:05) * edwarnicke says that in the absence of the cost, there’s the question of using jira vs. bugzilla (tbachman, 17:51:33) * colindixon says that his perception from the mailing list was that people preferrred Jira, but there’s a big cost (tbachman, 17:52:41) * colindixon asks that cost aside, are folks opposed to moving to Jira (tbachman, 17:53:09) * alagalah asks if we’d adopt it to everything, or just use it for bug-tracking (tbachman, 17:53:20) * rovarga says we could start with bug-tracking, and add features as the community becomes more comfortable with it (tbachman, 17:53:44) * ChrisPriceAB recommends using Jira for planning as well (tbachman, 17:54:18) * colindixon says that his understanding is that not all plugins are available for opensource (tbachman, 17:54:34) * abhijitkumbhare says that most people have used bugzilla but not used Jira (tbachman, 17:55:41) * dneary says that bugzilla has difficulties related to scalability as you get more projects, versions, workflows (tbachman, 17:56:29) * tykeal notes that they run several jira instances for various projects (tbachman, 17:56:37) * rovarga recommends setting up some sort of sandbox where people can try out how their workflows would be (tbachman, 17:57:03) * ACTION: phrobb to investigate what it takes to get to the license, and what the licence would be for (colindixon, 17:57:08) * What tykeal meant is that dneary said that most of Bugzilla complaints are related to the UI failing to scale well to many projects, versions, complex workflows, etc (dneary, 17:57:46) * we’d like to set up a sandbox and maybe do a TWS call where we show it off (colindixon, 17:58:10) Meeting ended at 17:59:14 UTC. Action items, by person ----------------------- * ChrisPriceAB * ChrisPriceAB to work with rovarga, jmedved, et. al. to look into leveraging OPNFV infrastructure for performance measurements and * colindixon * colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade * colindixon to follow up with zxiiro and gzhao about version bumps on friday and monday to see if we need interim solutions * colindixon to add bug 3051 the the blocker list and get robert edit access * colindixon to take the issue of more staff for added hours to board * colindixon to draft changes to language around project lifecycles * gzhao * zxiiro and gzhao to send email to release asking projects to not cut stable/lithium without version bumping * zxiiro and gzhao to work to drive the version bump through projects using the dependency chart as a guide: it seems, like the next targets would be OVSDB and L2 Switch, followed by dlux * colindixon to follow up with zxiiro and gzhao about version bumps on friday and monday to see if we need interim solutions * jmedved * ChrisPriceAB to work with rovarga, jmedved, et. al. to look into leveraging OPNFV infrastructure for performance measurements and * LuisGomez * LuisGomez and tykeal and jamoluhrsen to work out getting a patch merged in openstack to view all historical performance data * rovarga * ChrisPriceAB to work with rovarga, jmedved, et. al. to look into leveraging OPNFV infrastructure for performance measurements and * tykeal * LuisGomez and tykeal and jamoluhrsen to work out getting a patch merged in openstack to view all historical performance data * zxiiro * zxiiro and gzhao to send email to release asking projects to not cut stable/lithium without version bumping * zxiiro and gzhao to work to drive the version bump through projects using the dependency chart as a guide: it seems, like the next targets would be OVSDB and L2 Switch, followed by dlux * colindixon to follow up with zxiiro and gzhao about version bumps on friday and monday to see if we need interim solutions People present (lines said) --------------------------- * tbachman (117) * colindixon (32) * alagalah (18) * ChrisPriceAB (12) * edwarnicke (11) * cdub (11) * odl_meetbot (8) * rovarga (7) * tykeal (7) * zxiiro (5) * snoble (5) * dbainbri (4) * dneary (4) * dfarrell07 (3) * abhijitkumbhare (3) * ebrjohn (2) * gzhao (1) * dlenrow (1) * jmedved (1) * mohnish (1) * LuisGomez (1) Generated by `MeetBot`_ 0.1.4