#opendaylight-meeting: tsc

Meeting started by colindixon at 16:59:26 UTC (full logs).

Meeting summary

  1. agenda bashing and roll call (colindixon, 16:59:34)
    1. colindixon (colindixon, 16:59:36)
    2. Kent Watsen (kwatsen, 17:00:03)
    3. regXboi (regXboi, 17:00:38)
    4. Chris Price (ChrisPriceAB, 17:01:02)
    5. https://wiki.opendaylight.org/view/TSC:Main#Agenda (colindixon, 17:01:09)
    6. Luis Gomez (LuisGomez, 17:02:42)
    7. mohnish (mohnish, 17:03:19)
    8. edwarnicke (edwarnicke, 17:04:46)
    9. jmedved (jmedved, 17:06:03)
    10. it appears that action items (with the exception of master being stuck) have been addressed (regXboi, 17:06:31)
    11. ACTION: gzhao and edwarnicke to continue to work on getting master (Lithium) auto-release back unstuck (colindixon, 17:06:42)
    12. https://meetings.opendaylight.org/opendaylight-meeting/2014/tsc/opendaylight-meeting-tsc.2014-10-23-16.59.html old action items (regXboi, 17:07:00)

  2. new TSC members (colindixon, 17:08:43)
    1. regXboi welcomes luis (regXboi, 17:09:15)
    2. welcome LuisGomez to the TSC (colindixon, 17:09:17)
    3. LuisGomez is replacing dmm as brocade's platinum member designate (regXboi, 17:10:02)

  3. Updates (regXboi, 17:10:57)
    1. no updates on events (regXboi, 17:11:05)
    2. updates for system integration/testing and stable/helium both from Luis (regXboi, 17:11:34)
    3. plan to have proposal for integration/testing requirements my next TSC call (regXboi, 17:12:29)
    4. primary pain point continues to be infrastructure (regXboi, 17:12:50)
    5. all integration pieces for stable/helium are now complete - continuous testing of stable/helium is now ongoing (regXboi, 17:13:34)
    6. there is a RC for stable/helium .... status hopefully forthcoming in a linked email? (regXboi, 17:14:20)
    7. https://jenkins.opendaylight.org/odlautorelease/job/autorelease-helium-worker/ the job building helium stable pre-release (colindixon, 17:14:21)
    8. ACTION: gzhao/luis to send mail to discuss that the last day to have a patch merged to stable/helium is sunday 11/2. (regXboi, 17:16:29)
    9. https://docs.google.com/spreadsheets/d/1PYxjiSYEks44uJByVO1P44rnI5xTJRulpKyrSsDQF9g/edit#gid=1307630876 (LuisGomez, 17:16:36)
    10. project status (LuisGomez, 17:16:45)
    11. https://lists.opendaylight.org/pipermail/release/2014-October/000777.html the mail saying when the final artifacts will be cut (regXboi, 17:17:05)
    12. ACTION: gzhao to send email to release/discuss that stable/helium RC will be cut on monday and projects should test it and report as TSC will vote on that RC on next thursday's meeting (regXboi, 17:18:32)
    13. https://wiki.opendaylight.org/view/Simultaneous_Release:Cutting_Stability_Branches (colindixon, 17:19:20)
    14. question on what the completed through tab of project status means (regXboi, 17:19:32)
    15. answer this how far through the cutting stabilty branches process (regXboi, 17:19:50)
    16. https://wiki.opendaylight.org/view/Simultaneous_Release:Cutting_Stability_Branches cutting stability branches process (regXboi, 17:20:10)
    17. ACTION: colindixon to talk to LF marketing around co-ordinating any PR around stable release (in a week) (alagalah, 17:21:42)
    18. no Creation Reviews and no Committer Promotions (regXboi, 17:22:04)

  4. ovsdb splitting in two (regXboi, 17:22:34)
    1. Srini describes that the OVSDB project contains two components, north and southbound today. (ChrisPriceAB, 17:23:25)
    2. There is an ongoing discussion about splitting the project into two parts, he proposes a project called OVSDB plugin and openstack (ChrisPriceAB, 17:24:14)
    3. it is not clear that this discussion has been public ... i.e. we're still looking for public artifacts (regXboi, 17:24:52)
    4. Colindixon states that any project can split any time prior to M3 of a release plan. Pending creation reviews of the proprosed projects (ChrisPriceAB, 17:25:06)
    5. there is a patch planned for the openflowplugin project to include the "Nicira extentions" currently in OVSDB. (ChrisPriceAB, 17:27:12)
    6. https://lists.opendaylight.org/pipermail/ovsdb-dev/2014-October/000750.html ovsdb split proposal thread (regXboi, 17:27:30)
    7. ACTION: colindixon to make the possibitliy of adding new topics for agenda bashing more explicit on the TSC agenda (colindixon, 17:29:56)

  5. OPNFV (colindixon, 17:30:03)
    1. https://www.opnfv.org/ (regXboi, 17:30:12)
    2. https://wiki.opnfv.org/ the wiki (analogous to our OpenDayilght wiki) (colindixon, 17:30:53)
    3. OPNFV is about 1.5 months old and plans to work with “upstream” projects, e.g., in OpenStack and OpenDaylight to define an Open Platform for NFV (colindixon, 17:33:14)
    4. the intent is that most (maybe all) code will go to upstream projects (colindixon, 17:33:31)
    5. similar to ODL, there are open TSC meetings and feel free to join in (colindixon, 17:33:49)

  6. infrastructure update (colindixon, 17:41:09)
    1. there are templates in the releng/builder repo (colindixon, 17:41:19)
    2. projects that want want to try it out should contact Thanh (colindixon, 17:41:40)
    3. ACTION: colindixon to add infrastucture to the list of deafualt update (colindixon, 17:42:09)
    4. the directories contain a readme that will allow early adopters to spawn a jenkins docker image and get started with jenkins builder (regXboi, 17:42:18)
    5. colindixon asks if projects can be both in their jenkins silo and the new unified silo at the same time (colindixon, 17:45:50)
    6. the answer is that should be possible with a few possible quirks, for instance two jobs pushing to nexus from two places and two jobs voting in gerrit (colindixon, 17:46:55)
    7. colindixon volunteers TTP and alagalah volunteers GBP to participate (colindixon, 17:47:45)
    8. a question asked: "is there a target date for when projects that want to move should have moved?" (regXboi, 17:48:00)
    9. answer: no target date set as of now (regXboi, 17:48:12)
    10. skipping progress on technical debt/integration to ... (regXboi, 17:49:07)

  7. lithium release plan (regXboi, 17:49:14)
    1. https://wiki.opendaylight.org/view/Simultaneous_Release:DRAFT_Lithium_Release_Plan_ckd (regXboi, 17:49:52)
    2. previous link is draft lithium release plan (regXboi, 17:50:14)
    3. https://wiki.opendaylight.org/index.php?title=Simultaneous_Release%3ADRAFT_Lithium_Release_Plan_ckd&diff=22026&oldid=21676 changes to draft plan (regXboi, 17:50:33)
    4. colindixon noticed that the last date for project joining is a friday, which doesn't quite line up with the thursday TSC schedule (regXboi, 17:52:58)
    5. discussion of API declaration at M2 between colindixon and edwarnicke (regXboi, 18:00:29)
    6. ACTION: colindixon and edwarnicke to craft language around API declaration at M2 to achieve something useful but not overbearing (regXboi, 18:02:39)
    7. https://wiki.opendaylight.org/view/Simultaneous_Release:DRAFT_Release_Plan_2014_Template the per-project release plan template (colindixon, 18:04:26)
    8. question of what the default state should be. colindixon feels that if all APIs are enunciated, default status is less important (regXboi, 18:04:33)
    9. point that the release plan template now includes a section to be filled out by other teams that see a dependency (regXboi, 18:07:25)
    10. edwarnicke asks if we should make it possible for external projects, e.g., OPNFV to make requests of projects as part of negotiation (colindixon, 18:10:51)
    11. dlenrow says his intent is to try to get OPNFV to create a project in ODL to manage this (colindixon, 18:15:02)
    12. uri and edwarnicke point out that they really want to push the code into ODL directly (colindixon, 18:15:20)
    13. ACTION: colindixon to add a note that you need to send a mail along with putting the request on the providing project’s release plan for API negotiation (colindixon, 18:18:27)
    14. abhijitkumbhare asks if we should use bugzilla to track these things (colindixon, 18:18:45)
    15. edwarnicke and colindixon say there should probabably be a way to link to a bug representing the request (colindixon, 18:19:14)
    16. next subtopic: should there be requirements sonar code coverage/quality beyond reporting (regXboi, 18:21:55)
    17. Jan represents his and robert's view that we should be having a requirement to ensure overall code coverage/quality (regXboi, 18:23:46)
    18. regXboi asks (1) what about non-java code? (2) it seems to make senes that we report it in Lithium with the express intent of requiring coverage and lack of findbugs Beryllium (colindixon, 18:24:56)
    19. colindixon agrees with everything Jan said (as does regXboi) (regXboi, 18:25:20)
    20. colindixon also notes that blind reaching for code coverage can do more harm than good (colindixon, 18:27:05)
    21. edwarnicke notes that he likes the principle of reporting first before requiring (colindixon, 18:27:41)
    22. edwarnicke also notes that code coverage is a double edge sword, all it does is tell you that some measured behavior of the code hasn’t changed, it can actually bake in bugs rather than find them (colindixon, 18:29:09)
    23. regXboi proposes the idea of encouraging the key infrastructure projects to voluntairly try to hit certain code coverage and findbugs in their projects (colindixon, 18:31:48)
    24. jmedved, colindixon, and edwarnicke all say this sounds like the right approach (colindixon, 18:32:08)
    25. jmedved, colindixon, and edwarnicke all say this sounds like the right approach (apologies for double if that happens) (regXboi, 18:33:12)
    26. regXboi also adds that we should note that doing this will be viewed positively when it comes to moving along the lifecycle phases (colindixon, 18:33:50)
    27. flaviof asks if there’s a way to codify good logging processes as part of this and make that something we can encourage (colindixon, 18:34:40)
    28. https://wiki.opendaylight.org/view/Logging_Best_Practices (edwarnicke, 18:35:26)
    29. colindixon proposes maybe opening logging bugs, edwarnicke extends this to having a logging component in all projects so that we can track how bad the logging problem is as the bugs come in (colindixon, 18:37:02)
    30. regXboi asks if we start to tighten up the logging practices release, by release (colindixon, 18:37:28)
    31. ACTION: colindixon to work with gzhao to try to get project to create logging components in each project (colindixon, 18:41:09)
    32. a debate about whether all the the features need to be KDC (known, doable, confirmable) before the release starts (colindixon, 18:48:44)
    33. the key point seems to be around documentation requirements (colindixon, 18:48:58)
    34. edwarnicke is of the opinion that if it’s not KDC at the start of the release, it shouldn’t be required as part of this release plan (colindixon, 18:52:29)
    35. colindixon says that can be carried to an extreme where the release plan doesn’t ever start (colindixon, 18:52:48)
    36. ACTION: colindixon to reach out to integration and documentation to write requirements ASAP (colindixon, 18:53:41)
    37. edwarnicke also wants to see a full 4 weeks between when we approve the release plan and M1 (colindixon, 18:57:26)
    38. edwarnicke wants to see all the requirements explained clearly *before* we approve the release plan, and points out that the TSC has been bad at meeting deadlines to provide thing in the future (colindixon, 19:00:32)
    39. ACTION: regXboi to create a draft version of documentation requirements for Lithium (colindixon, 19:00:52)
    40. ACTION: colindixon to make sure we make it clear when the developer pre-milestone meeting (colindixon, 19:03:22)


Meeting ended at 19:03:26 UTC (full logs).

Action items

  1. gzhao and edwarnicke to continue to work on getting master (Lithium) auto-release back unstuck
  2. gzhao/luis to send mail to discuss that the last day to have a patch merged to stable/helium is sunday 11/2.
  3. gzhao to send email to release/discuss that stable/helium RC will be cut on monday and projects should test it and report as TSC will vote on that RC on next thursday's meeting
  4. colindixon to talk to LF marketing around co-ordinating any PR around stable release (in a week)
  5. colindixon to make the possibitliy of adding new topics for agenda bashing more explicit on the TSC agenda
  6. colindixon to add infrastucture to the list of deafualt update
  7. colindixon and edwarnicke to craft language around API declaration at M2 to achieve something useful but not overbearing
  8. colindixon to add a note that you need to send a mail along with putting the request on the providing project’s release plan for API negotiation
  9. colindixon to work with gzhao to try to get project to create logging components in each project
  10. colindixon to reach out to integration and documentation to write requirements ASAP
  11. regXboi to create a draft version of documentation requirements for Lithium
  12. colindixon to make sure we make it clear when the developer pre-milestone meeting


Action items, by person

  1. colindixon
    1. colindixon to talk to LF marketing around co-ordinating any PR around stable release (in a week)
    2. colindixon to make the possibitliy of adding new topics for agenda bashing more explicit on the TSC agenda
    3. colindixon to add infrastucture to the list of deafualt update
    4. colindixon and edwarnicke to craft language around API declaration at M2 to achieve something useful but not overbearing
    5. colindixon to add a note that you need to send a mail along with putting the request on the providing project’s release plan for API negotiation
    6. colindixon to work with gzhao to try to get project to create logging components in each project
    7. colindixon to reach out to integration and documentation to write requirements ASAP
    8. colindixon to make sure we make it clear when the developer pre-milestone meeting
  2. edwarnicke
    1. gzhao and edwarnicke to continue to work on getting master (Lithium) auto-release back unstuck
    2. colindixon and edwarnicke to craft language around API declaration at M2 to achieve something useful but not overbearing
  3. regXboi
    1. regXboi to create a draft version of documentation requirements for Lithium
  4. UNASSIGNED
    1. gzhao/luis to send mail to discuss that the last day to have a patch merged to stable/helium is sunday 11/2.
    2. gzhao to send email to release/discuss that stable/helium RC will be cut on monday and projects should test it and report as TSC will vote on that RC on next thursday's meeting


People present (lines said)

  1. colindixon (75)
  2. regXboi (61)
  3. alagalah (24)
  4. ChrisPriceAB (18)
  5. odl_meetbot (9)
  6. edwarnicke (5)
  7. flaviof (4)
  8. LuisGomez (4)
  9. mohnish (3)
  10. dfarrell07 (2)
  11. jmedved (2)
  12. cdub (2)
  13. tykeal (1)
  14. zxiiro (1)
  15. kwatsen (1)
  16. srini084 (1)


Generated by MeetBot 0.1.4.