#opendaylight-meeting: tsc

Meeting started by colindixon at 17:00:11 UTC (full logs).

Meeting summary

  1. agenda bashing and roll call (colindixon, 17:00:16)
    1. colindixon (colindixon, 17:00:24)
    2. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=49599 today's agenda (colindixon, 17:00:31)
    3. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-09-01-17.02.html last week's meeing minutes (colindixon, 17:00:48)
    4. rovarga for jmedved (rovarga, 17:01:16)
    5. Gal Mainzer (proxy for gkaempfer) (gmainzer, 17:01:33)
    6. Chris price (ChrisPriceAB, 17:01:52)
    7. Daniel Farrell (dfarrell07, 17:02:11)
    8. adetalhouet (adetalhouet, 17:02:24)
    9. abhijitkumbhare (abhijitkumbhare, 17:02:30)
    10. ACTION: colindixon to add APAC time TSC meeting to next week's meeting agenda http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_f447623d29817bc7 (colindixon, 17:02:41)
    11. ACTION: colindixon to add upgrades as Carbon Dev Forum topic (colindixon, 17:03:03)
    12. ACTION: rovarga will follow up with jira, group management, and user provisioning (colindixon, 17:03:21)
    13. ACTION: dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion (rovarga, 17:03:49)
    14. Anil Vishnoi (avishnoi, 17:04:01)
    15. ACTION: dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion (colindixon, 17:04:09)
    16. ACTION: colindixon to schedule when can we schedule the TCP-MD5 termination review (colindixon, 17:05:54)

  2. TSC mailing list votes and discussions (colindixon, 17:07:32)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-September/005924.html VOTE on TSC Election RGs (colindixon, 17:07:43)
    2. https://lists.opendaylight.org/pipermail/tsc/2016-September/005926.html VOTE on resolving vote-per-person vs. vote-per-interest (colindixon, 17:08:03)
    3. for other topics see agenda (colindixon, 17:08:04)

  3. events (colindixon, 17:08:13)
    1. https://www.opendaylight.org/global-events (colindixon, 17:08:21)
    2. we have a summit on 9/27-29 (colindixon, 17:08:29)
    3. https://wiki.opendaylight.org/view/Events:Carbon_Dev_Forum (jamoluhrsen, 17:08:41)
    4. https://wiki.opendaylight.org/view/Events:Carbon_Dev_Forum <--- DDF topics wiki (jamoluhrsen, 17:08:55)
    5. https://wiki.opendaylight.org/view/Events:Carbon_Dev_Forum please add any topics you want to for the Carbon DDF and add your name to the topics that you're interested in (phrobb uses that when scheduling) (colindixon, 17:08:56)
    6. phrobb will be scheduling things starting early next week, so please get things in now (colindixon, 17:09:40)
    7. tykeal is planning to run a keysigning on the second day, send your keys in if you want to participate (colindixon, 17:10:21)

  4. Boron (colindixon, 17:10:36)
    1. https://lists.opendaylight.org/pipermail/discuss/2016-August/006803.html GPG keysigning email (tykeal, 17:10:43)
    2. https://wiki.opendaylight.org/view/Simultaneous_Release/Boron/Status <--- Boron Status (anipbu, 17:11:57)
    3. http://meetings.opendaylight.org/opendaylight-meeting/2016/release/opendaylight-meeting-release.2016-09-07-21.55.log.html yesterday's technical analysis (rovarga, 17:12:26)
    4. https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=294913046 <--- Please see Section on DLUX 20 Patches for the related bugs and patches (anipbu, 17:24:23)
    5. colindixon notes that the marketing folks at LF have decide to postpoin the announcement until 9/21 (so 9 more days past monday) (colindixon, 17:26:24)
    6. colindixon says it's frustrating trade-off between not giving users a feature that seems really good, and merging 20 patches that weren't presented until the last minute despite many opportunities to raise this issue (colindixon, 17:27:22)
    7. vishnoianil notes that he'd really like to take the contribution and as a PTL and developer he'd love to see us fold these patches in, but as a TSC member he wants to draw a line in the sand (colindixon, 17:29:36)
    8. abhijitkumbhare asks what the risk is of not having this in, rovarga says his understanding is that the new feature is basically not functional (colindixon, 17:31:21)
    9. daniel malachovsky says that the fixes are just for the yangman application, it's basically a rework of the YangUI (colindixon, 17:31:49)
    10. daniel says he'd like deprecte YangUI in Boron, and remove it in Carbon, which can't be done without this (colindixon, 17:35:57)
    11. colindixon says that we have two other blocking bugs: (1) a potential performance degradation in OpenFlow plugin and (2) a blocker in honeycomb/vbd (colindixon, 17:37:56)
    12. adetalhouet says that the root of this issue was around not having enough committers on DLUX and that resulted in these patches not being cherry-picked before the release, (colindixon, 17:38:31)
    13. adetalhouet says that the TSC should be tracking the number of active committers per project so that we can make sure we catch things like this (colindixon, 17:39:13)
    14. vishnoianil agrees with that (colindixon, 17:39:36)
    15. ACTION: colindixon anipbu and phrobb to start a discussion about better tracking committer activity in projects (colindixon, 17:40:12)
    16. abhijitkumbhare notes that the openflow plugin issue isn't a regression, it was present in Beryllium, there is no performance shift in our testing, but our testing goes only for 10/30 minutes (colindixon, 17:44:13)
    17. the honeycomb/vbd blocking bug about removing bridgedomains ocassionaly, it was fixed before, but the forgotten and the regression was found today (colindixon, 17:45:45)
    18. Frank says that the current patch still needs more work, the bug results in stale state (colindixon, 17:47:11)
    19. colindixon says that his take based on our typical guidance has been that it's good to release on time, but it's better to deliver software with fewer known bugs and stronger (colindixon, 17:49:43)
    20. anipbu asks when Frank can get a fix, Frank says he hopes tomorrow, but he doesn't know because there isn't a root cause (colindixon, 17:53:38)
    21. colindixon says the plan is to fix the three blocking bugs ASAP and respin once we have them, but no later than 11:59p UTC on sunday, then basically get go-nogo votes and test to vote on releasing by next TSC meeting (colindixon, 18:01:37)
    22. the TSC will have a *very* high bar for what is a blocking bug after that, e.g., it's not clear to colindixon that any of the three above bugs would meet that critiria (colindixon, 18:03:51)
    23. Thanks opnfv and frankbrockners for finding that bug :) (dfarrell07, 18:05:29)

  5. cookies (colindixon, 18:05:31)


Meeting ended at 18:05:35 UTC (full logs).

Action items

  1. colindixon to add APAC time TSC meeting to next week's meeting agenda http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_f447623d29817bc7
  2. colindixon to add upgrades as Carbon Dev Forum topic
  3. rovarga will follow up with jira, group management, and user provisioning
  4. dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion
  5. dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion
  6. colindixon to schedule when can we schedule the TCP-MD5 termination review
  7. colindixon anipbu and phrobb to start a discussion about better tracking committer activity in projects


Action items, by person

  1. anipbu
    1. colindixon anipbu and phrobb to start a discussion about better tracking committer activity in projects
  2. colindixon
    1. colindixon to add APAC time TSC meeting to next week's meeting agenda http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_f447623d29817bc7
    2. colindixon to add upgrades as Carbon Dev Forum topic
    3. dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion
    4. dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion
    5. colindixon to schedule when can we schedule the TCP-MD5 termination review
    6. colindixon anipbu and phrobb to start a discussion about better tracking committer activity in projects
  3. dfarrell07
    1. dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion
    2. dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion
  4. phrobb
    1. colindixon anipbu and phrobb to start a discussion about better tracking committer activity in projects
  5. rovarga
    1. rovarga will follow up with jira, group management, and user provisioning


People present (lines said)

  1. colindixon (47)
  2. rovarga (8)
  3. abhijitkumbhare (6)
  4. LuisGomez (5)
  5. dfarrell07 (4)
  6. odl_meetbot (4)
  7. edwarnicke (4)
  8. lori (4)
  9. anipbu (4)
  10. adetalhouet (3)
  11. tykeal (2)
  12. jamoluhrsen (2)
  13. avishnoi (1)
  14. ChrisPriceAB (1)
  15. gmainzer (1)
  16. phrobb (0)


Generated by MeetBot 0.1.4.