#opendaylight-meeting: tsc

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

Meeting summary

  1. roll call and agenda bashing (colindixon, 17:00:19)
    1. colindixon (colindixon, 17:00:32)
    2. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=57406#Agenda (colindixon, 17:00:37)
    3. https://meetings.opendaylight.org/opendaylight-meeting/2017/tsc/opendaylight-meeting-tsc.2017-05-26-03.30.html las week's meeting minutes (colindixon, 17:00:49)
    4. https://wiki.opendaylight.org/view/Simultaneous_Release:Carbon_Release_Plan#Schedule carbon SRs are updated based on votes of release dates (colindixon, 17:01:31)
    5. rovarga (rovarga, 17:01:43)
    6. ACTION: phrobb to bring the need for a security manager to the board (colindixon, 17:01:44)
    7. anipbu (anipbu, 17:01:48)
    8. ACTION: phrobb to bring the TSC replacement language to the board (colindixon, 17:01:50)
    9. ACTION: colindixon to look to see if any current security response team members would like to voluntarily step down for any reason (colindixon, 17:02:04)
    10. ACTION: colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way (colindixon, 17:02:19)
    11. ACTION: phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better at tutorials (colindixon, 17:02:24)
    12. Hideyuki (hideyuki, 17:02:29)
    13. lori (lori, 17:02:38)
    14. abhijitkumbhare (abhijitkumbhare, 17:02:50)
    15. https://git.opendaylight.org/gerrit/#/c/58124/ this is the beginnings of how to make it easy for projects to release without participating in a simultaneous release (colindixon, 17:03:10)
    16. Thanh (zxiiro, 17:03:22)
    17. shague (shague, 17:03:31)
    18. ACTION: colindixon to cerate a bug (or sometign) to track off-cycle release tools and docs (colindixon, 17:03:46)
    19. Anil Vishnoi (vishnoianil, 17:04:37)
    20. colindixon did notifiy people about Beryllium-SR5 not happening and discussing the CVEs both in docs and to security-announce (colindixon, 17:05:00)
    21. dfarrell07 wants to talk about IPR with incoming code (colindixon, 17:09:27)

  2. TSC mailing list votes and discussions (colindixon, 17:09:37)
    1. https://lists.opendaylight.org/pipermail/tsc/2017-June/007379.html We will move the APAC-time TSC call to Wed night/Thu morning (colindixon, 17:09:51)
    2. ACTION: colindixon to make sure TSC meeting invites are right (colindixon, 17:10:23)
    3. https://lists.opendaylight.org/pipermail/tsc/2017-June/007375.html Carbon-SR1 will release on 7/6/2017 (colindixon, 17:11:05)
    4. https://lists.opendaylight.org/pipermail/tsc/2017-June/007418.html Nitrogen release plan is approved (colindixon, 17:11:37)
    5. https://lists.opendaylight.org/pipermail/tsc/2017-June/007416.html We will kick all projects out of Nitrogen to start (colindixon, 17:11:49)

  3. events (colindixon, 17:12:22)
    1. https://www.opendaylight.org/global-events (colindixon, 17:12:29)
    2. https://wiki.opendaylight.org/view/Events:Main (colindixon, 17:12:35)
    3. everyone is in China for ONAP this week, OPNFV summit next week, and then LinuxCon Asia the week after (colindixon, 17:13:11)
    4. dfarrell07 has talks on ODL at the OPNFV summit (colindixon, 17:13:28)
    5. we had the DDF last week (colindixon, 17:13:50)
    6. ACTION: colindixon to send out mail about how to plan DDFs forward, some ideas are: regional topic-specific DDFs, colocating with other projects to do mega-DDFs (colindixon, 17:16:49)
    7. vishnoianil asks if we know why people aren't going, a lot of people have event fatigue (colindixon, 17:17:46)

  4. boron (colindixon, 17:18:57)
    1. https://wiki.opendaylight.org/view/Simultaneous_Release:Boron_Release_Plan#Schedule <--- The last regularly scheduled Boron-SR4 is next Thursday with a cutoff on Sunday 6/15/2017 at 23:59 UTC. (anipbu, 17:19:14)
    2. https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-boron/ <--- Boron Autorelease builds are healthy. (anipbu, 17:19:20)
    3. https://jenkins.opendaylight.org/releng/view/CLM/ <--- CLM failures are similar to that of Boron-SR3. Although each violation were not individually signed off, the analysis indicates similar violations as in previous releases. (anipbu, 17:19:34)
    4. https://bugs.opendaylight.org/show_bug.cgi?id=8623 <--- We will be using this bug to track General Boron-SR4 Security Concerns. (anipbu, 17:19:54)

  5. carbon (colindixon, 17:20:33)
    1. https://docs.google.com/spreadsheets/d/1VcB12FBiFV4GAEHZSspHBNxKI_9XugJp-6Qbbw20Omk/edit#gid=1746681968 <--- We are waiting on 3 projects to revise and merge their Carbon Release Notes: packetable. We are missing release notes from 2 projects: next, dlux. (anipbu, 17:20:36)
    2. per the above, vishnoianil says he thinks it's likely not that it's a 2-day event and event fatigue alone (colindixon, 17:23:23)
    3. zxiiro will branch carbon docs to fix a user issue (colindixon, 17:24:21)

  6. release manager (colindixon, 17:24:45)
    1. katie has stepped down as release manager (colindixon, 17:25:05)
    2. colindixon would like to see us create a TSC-appointed position called "release manager" and then call for nominees (colindixon, 17:26:59)
    3. rovarga asks what the job description is, anipbu says it's really two goals to track the release and facilitate projects coming together (colindixon, 17:27:23)
    4. ACTION: anipbu and colindixon to write up a short blurb about what a release manager actually does (colindixon, 17:27:46)
    5. abhijitkumbhare asks if it's a still a volunteer position, colindixon says yes (colindixon, 17:28:35)
    6. colindixon notes that after this we would need to call for nominees (colindixon, 17:28:43)
    7. anipbu and others thank katie for her work (colindixon, 17:29:59)
    8. anipbu offerst to help train anyone who wants to do it (colindixon, 17:31:41)

  7. nitrogen (colindixon, 17:31:44)
    1. https://lists.opendaylight.org/pipermail/release/2017-June/011123.html <--- Nitrogen M0 Offset 0 Status Due. Kindly request projects to declare their intent to participate in the Nitrogen Simultaneous Release. (anipbu, 17:32:47)
    2. https://wiki.opendaylight.org/view/Project_Proposals:Main#New_Pending_Creation_Review <--- Projects have until the next three weeks (Offset 0: 6/14; Offset 1: 6/21, Offset 2: 6/28) to submit their project proposals and still participate in Nitrogen. (anipbu, 17:32:57)
    3. https://bugs.opendaylight.org/show_bug.cgi?id=8580 <--- In Nitrogen, we will manually release odlparent artifacts. We will update releng/builder job, staging repository in nexus. This will affect the version bumping scripts. In future, projects can depend on range of odlparent versions. (anipbu, 17:33:29)
    4. https://wiki.opendaylight.org/view/Simultaneous_Release/Nitrogen/Karaf#Status <--- Nitrogen Karaf 4 Status (anipbu, 17:34:02)
    5. https://docs.google.com/spreadsheets/d/1MYyGLFWN2RzUkJl8XMzXQ-3zWuOrUCQpIS6ORbmf4_U/edit#gid=1274532933 <--- Nitrogen Karaf 4 Tracking Spreadsheet (anipbu, 17:34:26)
    6. TWS Session on Monday 6/12/2017 to discuss Nitrogen Karaf 4 Project Action Items (anipbu, 17:34:44)
    7. Plan of Action: (1) Remove int/dist from autorelease (done) (2) Remove all non-offset0 from autorelease and int/dist - Bug 8625 (3) Fix Karat 4 Dependency Resolution - Bug 8622 (4) Add int/dist back into autorelease - Bug 8626 (5) Individually add projects back into autorelease and int/dist as they stabilize their build. (anipbu, 17:34:52)
    8. https://lists.opendaylight.org/pipermail/tsc/2017-June/007427.html anipbu and others recommend that new projects submit their proposal but should delay participation until Oxygen (colindixon, 17:35:00)
    9. https://bugs.opendaylight.org/show_bug.cgi?id=8628 <---Removed Infrautils until it solves the dependency on nitrogen odlparent OR until nitrogen odlparent releases (anipbu, 17:35:56)
    10. https://bugs.opendaylight.org/show_bug.cgi?id=8627 <--- Change the way we install features for CSIT. We are not going to use featuresBoot any longer and install from the karaf shell instead. (anipbu, 17:36:10)
    11. https://bugs.opendaylight.org/show_bug.cgi?id=8622 <--- Karaf 4 Dependency Resolution. Four possible ways forward: (1) use the karaf 3 resolver in karaf 4 (2) fix all bundles/features to be reloadable (3) use dependency=true, which won't reload them (4) figure out if we can effectively enable --no-auto-refresh (anipbu, 17:36:36)
    12. https://lists.opendaylight.org/pipermail/release/2017-June/011173.html <--- Progress on old feature resolver in Karaf 4 (anipbu, 17:37:08)
    13. https://git.opendaylight.org/gerrit/#/c/58478/ <--- Sets up all karaf4-parent descendants to build distributions with (anipbu, 17:37:17)
    14. zxiiro is workign on a per-project release job that can release outside of autorelease and is nearly done (colindixon, 17:38:41)
    15. vrpolak asks if he should make a stable distribution or not, colindixon says that we can ignore it for now (colindixon, 17:40:09)
    16. jamoluhrsen asks if we should have a Karaf 3 distribtion in nitrogen or not to allow for more testing (colindixon, 17:43:04)
    17. colindixon and rovarga take the position that we shouldn't, if you want to test things, you can do the developement on top of carbon if you want to test things easier (colindixon, 17:43:41)
    18. enabling people who are working on new features before trying to get their features to come up in Karaf 4 seems bad (colindixon, 17:44:06)
    19. vishnoianil asks how confident are we that we'll get to karaf 4 in nitrogen (colindixon, 17:45:45)
    20. vishnoianil alsk asks if we have a backup plan if we can't moce to karaf 4 (colindixon, 17:45:58)
    21. colindixon says no, because if we can't migrate to karaf 4 in 2 months with it as our primary/only focus, then we need need to radically re-evaluate how the project works (colindixon, 17:47:05)
    22. VOTE: Voted on "shall we say that we will focus solely on Karaf 4 in nitrogen and not spend any cycles on karaf 3?" Results are, +1: 10, -1: 1 (colindixon, 17:50:02)
    23. shague is just concerned that we will be able to get Karaf 4 to work (colindixon, 17:51:08)
    24. colindixon notes that (to his knowledge) pretty much all projects should be able to start buildign and testing their local karaf 4 distribution to get it working (colindixon, 17:52:56)
    25. so everyone should be able to be doing something toward getting us onto karaf 4 (colindixon, 17:53:06)

  8. system integration and test (colindixon, 17:53:22)
    1. nothing major, Boron CSIT is still running daily, it will be weekly after SR4 (colindixon, 17:53:38)

  9. infastructure (colindixon, 17:53:48)
    1. we have had long queues (currently 142 down from 216 this morning east coast) (colindixon, 17:54:19)
    2. colindixon asks if we can purge jobs that don't do anything, nobody looks at, etc. (colindixon, 17:55:31)
    3. colindixon notes that verifies and merges are still going through, and it's been a bit slow, but not bad (colindixon, 17:56:28)

  10. pulling in commits from github to int/pack (colindixon, 17:57:12)
    1. https://lists.opendaylight.org/pipermail/tsc/2017-June/007435.html (colindixon, 17:57:39)
    2. dfarrell07 asks if he can pull that in (colindixon, 17:58:29)
    3. colindixon and edwarnicke say that for all the commits from dfarrell07 this shoudl be fine, if there are commits from others, we need to make sure they agree to the OpenDaylight DCO (colindixon, 17:59:08)
    4. edwarnicke notes that you really want the logging the approval from other authors as the commit history in the repo (colindixon, 17:59:55)

  11. cookies (colindixon, 18:01:44)


Meeting ended at 18:01:54 UTC (full logs).

Action items

  1. phrobb to bring the need for a security manager to the board
  2. phrobb to bring the TSC replacement language to the board
  3. colindixon to look to see if any current security response team members would like to voluntarily step down for any reason
  4. colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way
  5. phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better at tutorials
  6. colindixon to cerate a bug (or sometign) to track off-cycle release tools and docs
  7. colindixon to make sure TSC meeting invites are right
  8. colindixon to send out mail about how to plan DDFs forward, some ideas are: regional topic-specific DDFs, colocating with other projects to do mega-DDFs
  9. anipbu and colindixon to write up a short blurb about what a release manager actually does


Action items, by person

  1. anipbu
    1. anipbu and colindixon to write up a short blurb about what a release manager actually does
  2. colindixon
    1. colindixon to look to see if any current security response team members would like to voluntarily step down for any reason
    2. colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way
    3. colindixon to cerate a bug (or sometign) to track off-cycle release tools and docs
    4. colindixon to make sure TSC meeting invites are right
    5. colindixon to send out mail about how to plan DDFs forward, some ideas are: regional topic-specific DDFs, colocating with other projects to do mega-DDFs
    6. anipbu and colindixon to write up a short blurb about what a release manager actually does
  3. zxiiro
    1. colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way
  4. UNASSIGNED
    1. phrobb to bring the need for a security manager to the board
    2. phrobb to bring the TSC replacement language to the board
    3. phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better at tutorials


People present (lines said)

  1. colindixon (83)
  2. anipbu (23)
  3. odl_meetbot (12)
  4. vishnoianil (10)
  5. shague (7)
  6. abhijitkumbhare (5)
  7. jamoluhrsen (3)
  8. rovarga (2)
  9. zxiiro (2)
  10. dfarrell07 (2)
  11. hideyuki (2)
  12. lori (2)
  13. edwarnicke (1)
  14. CaseyODL (1)


Generated by MeetBot 0.1.4.