#opendaylight-integration: new release model

Meeting summary

1. 1. checkpoints should have list of members planning to contribute (jamoluhrsen, 17:09:17)
   2. midterm chkp should have status around feature development (is there csit, ut, etc.) (jamoluhrsen, 17:09:46)
   3. dfarrell07 makes the point that we really don't want any major gory details in these checkpoints, since there is nothing anyone can do if projects don't give them, or give them wrong, etc. (jamoluhrsen, 17:13:31)
   4. maybe we can ask in the checkpoints for projects to give a (paragraph form) high level explanation of what features are possibly coming (CKPT 1), what feature work is happening (CKPT 2) and did it happen (CKPT 3) (jamoluhrsen, 17:17:08)
   5. we don't need to do anything about those high level explanations (jamoluhrsen, 17:17:46)
   6. anipbu points out that we have tried ~4 times to do *something* around collecting quality metrics (dashboard, etc) and it never takes hold, so it's a bad idea to try to worry about quality metrics in this new release model (jamoluhrsen, 17:28:08)
   7. anipbu notes that we need people to really check the release plans, but I am not sure we were still having these formal release plans (jamoluhrsen, 17:36:08)
   8. with current checkpoint plan to automatically collect blocker jiras, etc. it means we require projects to file the jiras right and now we are dependent on projects to do it right. (jamoluhrsen, 17:54:10)
   9. https://git.opendaylight.org/gerrit/#/c/67539/ (bjohnson, 15:04:06)
   10. https://git.opendaylight.org/gerrit/#/c/67544/ (bjohnson, 15:04:31)

Action items

1. (none)

People present (lines said)

1. odp-gerritbot (31)
2. bjohnson (11)
3. jamoluhrsen (10)
4. dfarrell07 (9)
5. jaicaa (4)
6. odl_meetbot (3)