#opendaylight-devforum5: release for lithium

Meeting started by colindixon at 17:05:56 UTC (full logs).

Meeting summary

  1. current release pipeline (colindixon, 17:06:14)
    1. mlemay talks about how we currently do releases, all projects go through milestones at the same time, hitting the same things at the same dates (colindixon, 17:07:34)
    2. his point seems to be that inter-project dependencies mean that we really should have some delay between when the milestone for projects based on their dependency relationship (colindixon, 17:09:59)
    3. radical idea: no more simultaneous release (colindixon, 17:10:19)
    4. instead have gates, e.g., based on lack of bugs, code coverage, etc. (colindixon, 17:10:47)
    5. rovarga says that currently one big problem is that we have no visibility into project inter-dependencies (colindixon, 17:11:17)
    6. colindixon points out that this manifested as not being able to tell who meant to expose what APIs and who meant to consume what APis to track dependencies, reveal when APIs are deprecated, not yet stable, etc. (colindixon, 17:14:51)
    7. above was partially stealing from mlemay (not all colindixon) (colindixon, 17:15:12)
    8. goal is to fail early, catch CI failures faster for integration work (colindixon, 17:17:48)
    9. minor aside about docs and how to do docs, with lots of ideas, probably too much to cover here (colindixon, 17:18:25)
    10. colindixon talks about docs being managed like code (dfarrell07, 17:20:40)
    11. discussion about integration jobs, projects not knowing about them, therefore not doing them (dfarrell07, 17:20:59)
    12. tykeal suggests that we're not using our existing tools properly for int work (dfarrell07, 17:21:39)
    13. Need to rethink how we are using Jenkins, not used siloed Jenkins systems (via tykeal) (dfarrell07, 17:22:19)
    14. Silos are legicy issue, forced on tykeal before project even started (dfarrell07, 17:22:38)
    15. colindixon points out that we may be jumpping into (dfarrell07, 17:23:36)
    16. colindixon points out that we may be jumpping into "things are broken and we need new tools" too quickly (dfarrell07, 17:24:10)
    17. colindixin talks about semantic buid versions "what was the last version (nightly, weekly) that passed these jobs" (dfarrell07, 17:25:12)
    18. Question put as "should we have integration testing on snapshots or not". Currently just need your tests to pass, int tests happen after the fact. (dfarrell07, 17:26:04)
    19. tangent on versions for a while (colindixon, 17:27:08)
    20. Tic-toc relase mentioned: Relase "core", relase "projects", iterate every few months. Issues with what is "core" (dfarrell07, 17:27:32)
    21. "Core" may mean base infra pieces (dfarrell07, 17:28:17)
    22. colindixion Is working on wiki fixes to doc relase plan (dfarrell07, 17:28:42)
    23. tangent on versions, running multiple versions at a time, discussion about this maybe being a bad idea (dfarrell07, 17:31:16)
    24. Need to be able to take X vendor ODL controller, Y vendor app, they run together via colindixon (dfarrell07, 17:33:12)
    25. Releases (tic-toc vs simul) may be very different for leaf projects vs other projects (dfarrell07, 17:34:56)
    26. Discussion about offsets between deadlines, tic-toc is similar to this, again may be importantly different between types of projects (dfarrell07, 17:37:07)
    27. rovarga talks about API freeze vs feature freeze, ordering of the two (dfarrell07, 17:38:18)
    28. colindixon points out that we are a very new project, these issues smell like a product of getting projects spun up on how all release things work (dfarrell07, 17:40:09)
    29. "Are there issues we think are fundi broken; which are ones that will are ghosts and will go away without hard work" colindixon (dfarrell07, 17:42:00)
    30. We're kinda already doing tic-toc, just on 6 month cadence. MD-SAL introduced last release, used more this relase. (dfarrell07, 17:43:11)
    31. colindixon notes that our problem in Helium on APIs is that this is the first time many APIs were used and relied on by the community (such as Yangtools and MD-SAL) apis. (phrobb, 17:43:48)
    32. noted that this kind of API evolution will probably occur for 3 or 4 more releases (phrobb, 17:44:22)
    33. If we have infra that is maybe-not-working, why are we buidling on top of it? Need to focus on infra projects. cdub (dfarrell07, 17:44:51)
    34. cdub asks why we are continuing to build out features with the foundation is not strong. (phrobb, 17:45:03)
    35. many +1s to cdub's "make foundation strong" (dfarrell07, 17:45:38)
    36. colindixon asks "how many have lost sleep due to release?" (phrobb, 17:47:46)
    37. "what are the problems that caused us to loose sleep" (dfarrell07, 17:48:20)
    38. seeking agreement on what the problems are, colindixon is (dfarrell07, 17:50:36)
    39. one issue is version, simul release, how we integrate rovarga (dfarrell07, 17:51:02)
    40. Rob A talks about relase vehicle being < getting solid foundation features (dfarrell07, 17:51:53)
    41. moving to Karaf was a poin point, many +1s (dfarrell07, 17:52:06)
    42. Ryan points out that it's not just moving to Karaf, it's moving to new *anything critical* (dfarrell07, 17:52:33)
    43. infra needs to come early in relase cycle, rovarga says (thinking about Karaf) (dfarrell07, 17:53:21)
    44. Infra needs to be agreed on at summit, 3-4 months in advance of release rovarga (dfarrell07, 17:53:48)
    45. "Karaf will be only relase vehicle" was only decided at least TSC call, Lori Jakab says (dfarrell07, 17:54:20)
    46. phrobb points out that all of the above applies to docs, generally anything new, needs to be done early in cycle (dfarrell07, 17:55:20)
    47. many +1s to suffering from docs (dfarrell07, 17:55:34)
    48. Docs that have been vetted by others and linked from somewhare sane before we even talk about a feature being "ready", colindixon (dfarrell07, 17:56:26)
    49. schedule is badly broken, all things that need to be in next relase signed on during last release, cdub says (dfarrell07, 17:58:17)
    50. maybe waisting effort for new, less critical, projects to require lots of "we're going to do this" docs, Rob A (dfarrell07, 18:00:01)
    51. cdub: end of release should be boring, should be moving to next release (dfarrell07, 18:00:19)
    52. Incubaged projects vs stable/critical things need diff release cycles, foundation needs focus and to be a solid release (dfarrell07, 18:02:55)
    53. we are trying to put infrastructure on a more aggressive release schedule (rovarga, 18:04:03)
    54. such that we deliver key pieces of yangtools and mdsal early in the release cycle (rovarga, 18:04:09)
    55. "Release in expermentail once before can even be release in non-exp mode" colindixon (dfarrell07, 18:04:12)
    56. what we need better handle on (and hope to getout of the design summit) is the direction infrastructure _users_ need us to do (rovarga, 18:04:16)
    57. discussion about features vs projects vs more abstract "component" (dfarrell07, 18:05:38)
    58. and how the release discussion may be different between them (dfarrell07, 18:05:58)
    59. out of time (dfarrell07, 18:06:05)


Meeting ended at 18:06:23 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. dfarrell07 (55)
  2. colindixon (15)
  3. tykeal (8)
  4. rovarga (6)
  5. odl_meetbot (5)
  6. phrobb (4)
  7. regXboi (3)
  8. ChrisPriceAB (1)
  9. readams (1)


Generated by MeetBot 0.1.4.