#opendaylight-meeting Meeting

Meeting started by colindixon at 17:01:04 UTC (full logs).

Meeting summary

  1. overview (colindixon, 17:01:12)
    1. I'm going to try to keep this meeting to the tasks which are due today (or at least started by today) to keep things brief (colindixon, 17:01:34)

  2. Identify all places dependency versions in project pom.xml files are not current for all ODL Dependencies (colindixon, 17:03:22)
    1. AGREED: this item is done (colindixon, 17:04:19)
    2. note that this is "identify" and not fix (colindixon, 17:04:58)

  3. Identify differing versions of dependencies on external artifacts and negotiate a recommended version (colindixon, 17:05:08)
    1. the actual work per-project to update starts 1/15 (Madhu, 17:05:19)
    2. Madhu: external artifact dependencies are identified... but negotiation has not started yet. (colindixon, 17:06:00)
    3. ACTION: Madhu to e-mail out the list of external dependencies and their versions, and we'll start negotiating by 1/16 (colindixon, 17:08:07)
    4. Madhu has updated the start date for this task "Update dependency version on external artifacts to match across ODL" to 1/16 (colindixon, 17:09:03)
    5. maybe bring up the things individual projects are expected to do during the TSC meeting? (colindixon, 17:11:19)
    6. AGREED: we need to have a relatively low tolerance for open loop on these per-project tasks including removing log messages, fixing version dependencies, etc. (colindixon, 17:12:07)

  4. user manaual (colindixon, 17:12:30)
    1. since the relevant people aren't here, move this topic to this evening (colindixon, 17:13:03)

  5. general comments about the meeting (colindixon, 17:13:21)
    1. we should post attendance of project leads (colindixon, 17:13:36)
    2. this will enable loop closing (colindixon, 17:13:45)

  6. roll call of project leads (colindixon, 17:14:13)
    1. abhijitkumbhare is present: Openflowplugin (abhijitkumbhare, 17:15:13)
    2. Madhu for OVSDB & Release related global wrangling. (Madhu, 17:15:35)
    3. Luis for Inetgration and global testing (LuisGomez, 17:15:58)
    4. Anees for Open DOVE and platform qualification (Ryan will join also for Open DOVE) (ashaikh, 17:16:50)

  7. developer guide (colindixon, 17:17:57)
    1. again, chris price and rob dolin aren't present, hopefully we can do this in the evening meeting (colindixon, 17:18:12)

  8. Write recommendation for cutting Release Branches and laying Release labels (colindixon, 17:18:27)
    1. wrong topic, ignore this (colindixon, 17:18:53)

  9. Document how to cut release artifacts for a project (colindixon, 17:19:00)
    1. Release recommendation #link https://wiki.opendaylight.org/view/Simultaneous_Release:Simultaneous_Release_Plan_2014:ReleaseRecommendations (Madhu, 17:20:12)
    2. colindixon marked this task as done on the spreadsheet (colindixon, 17:20:59)

  10. Write recommendation for cutting Release Branches and laying Release labels (colindixon, 17:21:13)
    1. Madhu's instructions specify that you create a tag for release artifacts rather than a branch. edwarnicke is good with this because you can pull a branch from a tag easily. (colindixon, 17:23:11)
    2. maven-release-plugin does the tagging automatically (Madhu, 17:24:02)
    3. post-release, we need more integration jenkins job for RELEASE and new SNAPSHOTs (Madhu, 17:26:31)
    4. AGREED: developer guide should include a tag to the tag in the code for the release artifacts, colindixon will put it in the notes for the spreadsheet (colindixon, 17:28:13)
    5. the release management, versioning and branching recommendations are for Hydrogen release only. Post-Hydrogen release management discussions will be Post-Hydrogen ;) (Madhu, 17:29:48)
    6. Madhu and LuisGomez will work on providing recommendations for release branches and laying release labels the date will be moved (colindixon, 17:29:54)
    7. we will use the default behavior of maven-release-plugin to lay the release tag automatically. the branching from that can be managed manually. (Madhu, 17:32:58)

  11. Write Release Review Template (colindixon, 17:33:12)
    1. this is done and posted here #link https://wiki.opendaylight.org/view/Sample_Release_Review (colindixon, 17:33:26)
    2. http://www.opendaylight.org/project-lifecycle-releases#MatureReleaseProcess Unless others feel differently, my logic was that the TSC would want to (and may be limited by it's charter to) impose the minimum requirements as to not hold up any of the releases. (colindixon, 17:34:08)
    3. AGREED: this is done and marked as such on the spreadsheet (colindixon, 17:35:28)

  12. log level recommendations (colindixon, 17:35:36)
    1. HELP: we need somebody to volunteer for this (colindixon, 17:35:43)
    2. AGREED: dual_regXboi will pick this up and write up a short guide on how to pick proper log levels (colindixon, 17:37:38)
    3. AGREED: we'll move the log level recommendations deadline to 1/16 and if dual_regXboi can get it done early great (colindixon, 17:39:27)
    4. lots of comments for where dual_regXboi shoudl start looking (see the full log) (colindixon, 17:40:15)


Meeting ended at 17:40:20 UTC (full logs).

Action items

  1. Madhu to e-mail out the list of external dependencies and their versions, and we'll start negotiating by 1/16


Action items, by person

  1. Madhu
    1. Madhu to e-mail out the list of external dependencies and their versions, and we'll start negotiating by 1/16


People present (lines said)

  1. colindixon (110)
  2. Madhu (73)
  3. edwarnicke (25)
  4. dual_regXboi (14)
  5. regXboi (4)
  6. LuisGomez (4)
  7. phrobb (2)
  8. odl_meetbot (2)
  9. abhijitkumbhare (1)
  10. ashaikh (1)


Generated by MeetBot 0.1.4.