#opendaylight-meeting: tsc

Meeting started by phrobb at 17:01:03 UTC (full logs).

Meeting summary

    1. Chris Wright (cdub, 17:01:13)

  2. roll call and agenda (colindixon, 17:01:46)
  3. Roll Call (phrobb, 17:01:49)
    1. TSC members please #info in (phrobb, 17:02:00)
    2. lenrow (dlenrow, 17:02:00)
    3. Ivan Wood (IvanWood, 17:02:02)
    4. regXboi (regXboi, 17:03:01)
    5. EdM_ (edwarnicke, 17:03:24)
    6. edwarnicke (edwarnicke, 17:03:31)
    7. Kent Watsen (kwatsen, 17:04:32)
    8. https://wiki.opendaylight.org/view/TSC:Main#Meeting_Agenda (regXboi, 17:04:35)
    9. warning that we may not get to the Creation Review for today (regXboi, 17:05:09)
    10. cdub running meeting for dmm who may be late (regXboi, 17:05:38)

  4. Updates (regXboi, 17:05:44)
    1. discovery team is on standby for the creation review - no worries if it is not accomplished today (phudgins, 17:06:09)
    2. Phil reporting on events update - at 120 people for 9/29 Lithium meetup (regXboi, 17:06:09)
    3. we need people to RSVP to get accurate counts for the design forum (colindixon, 17:06:53)
    4. upcoming events includes hackfest in dusseldorf in October (regXboi, 17:06:56)
    5. as well as openstack summit in paris in November (regXboi, 17:07:12)
    6. Phil reporting on branding - it is still progressing through marketing with no update for today (regXboi, 17:07:58)

  5. elections (colindixon, 17:08:03)
    1. please vote, it closes soon (e-mails were sent) (colindixon, 17:08:12)
    2. Phil reporting on at-large elections - deadline is Monday - if you haven't voted, please do so (regXboi, 17:08:15)
    3. abhijitkumbhare proxy for Chris Price (my laptop had crashed - so did not info in earlier (abhijitkumbhare, 17:08:22)

  6. system integration/testing update (regXboi, 17:08:39)
    1. the Helium RC0 candidate is under test (regXboi, 17:08:58)
    2. there are issues that have been found that have been shared in email - these may be covered during Helium release status update (regXboi, 17:09:57)

  7. Documentation update (regXboi, 17:10:10)
    1. Manny reports that things are going to be tight for the core docs, but it looks like they will be published by 9/29 (regXboi, 17:10:41)
    2. open items remaining are CLI commnads for the controller and procedures for integrating the controller with other projects (regXboi, 17:11:03)
    3. cdub worries that this is a definite risk point (regXboi, 17:11:52)
    4. cdub notes we are a ways from the deadline, but what contingency plans do we have to complete documentation? (phrobb, 17:12:07)
    5. reply from Manny is that the scope has been pared way back but the documentation will still be "best-effort" given the new authors, tool set, etc. (regXboi, 17:12:56)

  8. Helium release status (colindixon, 17:13:54)
    1. https://docs.google.com/spreadsheets/d/1TRYposNDFPaKcySlvwkOXvfR6Anx2EFujlIjoTthhRY/edit (colindixon, 17:15:20)
    2. above link is current Helium release status (thanks Colin) (regXboi, 17:15:38)
    3. on the karaf tab, everyone is green or pending review except Defense4All (not started) and SDNi (work in progress) (colindixon, 17:16:18)
    4. on the General Tab, most are yellow (one red) (regXboi, 17:16:51)
    5. an existing issue is that the project contacts are not clear on what each of the milestones mean (regXboi, 17:17:24)
    6. and therefore the milestone status reported may not be 100% accurate (regXboi, 17:18:35)
    7. cdub points out that it’s probably an (odd) good sign that some projects are dropping out when they realize that they either won’t make it or aren’t a good fit (colindixon, 17:19:53)

  9. committer promotions (regXboi, 17:19:59)
    1. https://lists.opendaylight.org/pipermail/tsc/2014-September/001631.html (cdub, 17:20:13)
    2. https://docs.google.com/document/d/10Q_HV6qh52Pay_IQNv6EoJ0F6Z8M8nNrW0RZ4RNtRu0/edit (regXboi, 17:20:30)
    3. https://lists.opendaylight.org/pipermail/tsc/2014-September/001625.html (regXboi, 17:20:40)
    4. alagalah_ says that tbachman is #2 in code contributions on GBP (colindixon, 17:21:21)
    5. alagalah_ also notes that he’s also more than willing to help in the community pretty much everywhere (colindixon, 17:21:37)
    6. VOTE: Voted on "Shall the TSC promote Thomas Bachman to committer on the Group Based Policy project?" Results are, +1: 7 (phrobb, 17:22:26)
    7. AGREED: Thomas Bachman to committer on the Group Based Policy project (regXboi, 17:22:37)
    8. gzhao notes that tbachman has also helped moving projects to Karaf in huge ways (colindixon, 17:22:37)

  10. time and location for RC1 cutting (colindixon, 17:24:48)
    1. the issue is that we would like clarity about when your patches have to be in (and on what branch) in order to be part of the RC1 cutting (colindixon, 17:25:45)
    2. Madhu notes time/date of RC1 is dependent on Release Vehicles (phrobb, 17:26:49)
    3. colindixon notes this discussion is just pick a time of day and a location (branch) where to cut from (phrobb, 17:27:28)
    4. edwarnicke asks that we determine time of day first: (phrobb, 17:28:12)
    5. phrobb proposes midnight UTC which is 5p pacific (colindixon, 17:29:25)
    6. AGREED: midnight UTC for time of day to cut RC1 (phrobb, 17:29:57)
    7. http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140916T00 this is the (assuming it stays 9/15) for those who want help converting (colindixon, 17:31:48)
    8. the section question on the table is when do people cut over to helium/stable branches and when does autorelease pull from that instead of master (colindixon, 17:33:13)
    9. edwarnicke notes that we have a note in the release plan that says projects *must* create a helium/stable branch on/before 9/29 when we do our release (colindixon, 17:34:00)
    10. abhijitkumbhare points out that really, the only reason you would need a helium/stable branch is to work on lithium, so maybe we can push this off unless people need that (colindixon, 17:35:24)
    11. rovarga says that actually the ability to have a branch where you can keep relatively few patches right now so that people can target their reviews to those targetted at helium would help even without that (colindixon, 17:36:00)
    12. regXboi notes that because our relaese plan said projects don’t have to do release/helium until the last second, so our hands may be tied (colindixon, 17:37:42)
    13. cdub proposes RC1 cut from master, and stick with RCs coming from master through Helium (phrobb, 17:39:08)
    14. above, abhijitkumbhare actually said “the only reason you would need a helium/stable branch is to work on lithium, so do we know are any projects working right now toward Lithium?” (colindixon, 17:39:13)
    15. edwarnicke notes that one project has a "development" branch and asks that they don't have to move (colindixon, 17:40:09)
    16. VOTE: Voted on "we will cut from the same branches for RC1& RC2 as we did for RC0 (mostly master, but some projects may be on other branches as noted above)?" Results are, +1: 6 (phrobb, 17:43:54)
    17. AGREED: we will cut from the same branches for RC1& RC2 as we did for RC0 (mostly master, but some projects may be on other branches as noted above) (regXboi, 17:43:57)
    18. AGREED: all projects *must* cut helium/stable branches on or before 9/29 (this was agreed on in the past, but reiterated here) (colindixon, 17:44:20)

  11. articulate criteria for RC1 (regXboi, 17:45:17)
    1. phil proposes: 1 Contains all projects (ie all projects have their karaf features submitted to Integration) (regXboi, 17:46:16)
    2. phil propose: 2 All projects are code-frozen (several projects were not code frozen for RC0) (regXboi, 17:46:27)
    3. phil proposes: 3 If a project cannot meet these two criteria by RC1 (Monday, Sept 15th), then they will be dropped from the project - and/or if the TSC wishes the project could apply for an exception - giving a reason (like they have no other projects depending on them) and a drop dead date (like Sept 17th) when they will have the two items above complete. (regXboi, 17:46:40)
    4. https://meetings.opendaylight.org/opendaylight-meeting/2014/helium_pre_rc0_rc1/opendaylight-meeting-helium_pre_rc0_rc1.2014-09-10-15.30.html (regXboi, 17:46:51)
    5. request of what projects don't meet these two criteria (regXboi, 17:47:59)
    6. answer there are three projects that are not in a state to participate in RC1 and these are leaf projects (regXboi, 17:48:44)
    7. they are SDNi, Defense4All, plugin2oc (colindixon, 17:49:26)
    8. request for what projects aren't code-frozen (regXboi, 17:49:53)
    9. we don’t have data for code-frozen today, but from M5: 4 projects that have not dropped out (packetcable, sfc, snmp4sdn, vtn) (regXboi, 17:50:48)
    10. hideyuki says that VTN will be code-frozen by RC1 (colindixon, 17:51:55)
    11. https://meetings.opendaylight.org/opendaylight-meeting/2014/tsc/opendaylight-meeting-tsc.2014-07-31-16.59.log.html (tbachman, 17:53:47)
    12. irc://irc.freenode.net:6667/#startvote shall the criteria for RC1 is 1) karaf features successfully merged to integration, and 2) you must be code frozen? -1, 0, +1 (phrobb, 17:58:07)
    13. VOTE: Voted on "shall the criteria for RC1 is 1) karaf features submitted to integration, and 2) you must be code frozen?" Results are (regXboi, 17:58:37)
    14. VOTE: Voted on "shall the criteria for RC1 is 1) karaf features successfully merged to integration, and 2) you must be code frozen?" Results are, +1: 6 (regXboi, 17:59:21)
    15. AGREED: the criteria for RC1 shall be 1) karaf features successfully merged to integration, and 2) you must be code frozen (regXboi, 17:59:39)
    16. now what to do about exception versus dropped... (regXboi, 17:59:54)
    17. cdub proposes being harsh and just saying they are dropped (regXboi, 18:00:13)
    18. edwarnicke agrees (colindixon, 18:00:18)
    19. edwarnicke agrees with cdub (regXboi, 18:00:20)
    20. VOTE: Voted on "If a project does not meet the criteria for RC1, the project will be dropped from the Helium Release?" Results are, 0: 1, +1: 5 (phrobb, 18:03:41)
    21. AGREED: If a project does not meet the criteria for RC1, the project will be dropped from the Helium Release (regXboi, 18:03:54)
    22. the record should show that dlenrow voted in favor on the previous measure (although it was not required) (colindixon, 18:04:52)
    23. ACTION: gzhao to (aggressively) follow up with project not meeting the RC1 criteria so that they have the best chance of not being dropped (colindixon, 18:05:49)


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

Action items

  1. gzhao to (aggressively) follow up with project not meeting the RC1 criteria so that they have the best chance of not being dropped


Action items, by person

  1. gzhao
    1. gzhao to (aggressively) follow up with project not meeting the RC1 criteria so that they have the best chance of not being dropped


People present (lines said)

  1. regXboi (74)
  2. colindixon (65)
  3. odl_meetbot (38)
  4. phrobb (21)
  5. tbachman (15)
  6. edwarnicke (12)
  7. alagalah_ (10)
  8. dlenrow (9)
  9. cdub (8)
  10. abhijitkumbhare (7)
  11. IvanWood (5)
  12. kwatsen (3)
  13. gzhao (2)
  14. hideyuki (2)
  15. phudgins (1)


Generated by MeetBot 0.1.4.