#opendaylight-integration: integration

Meeting summary

1. infra (jamoluhrsen, 05:05:56)
   1. there was a infra controller issue causing jobs to fail, but it's since been resolved. (jamoluhrsen, 05:06:35)
   
   
2. release (jamoluhrsen, 05:07:12)
   1. neon sr3 release is done and abelur will do the packaging work. (jamoluhrsen, 05:07:28)
   2. we still need to update the docs for the release (jamoluhrsen, 05:07:47)
   3. ACTION: abelur to ping David to do the docs update (jamoluhrsen, 05:07:58)
   4. sodium SR2 is due 1/30 (jamoluhrsen, 05:11:02)
   5. so we will need to lock sodium on 1/23 and that's when we can take a release candidate build (jamoluhrsen, 05:12:26)
   6. Mg release will go code freeze (branch lock) at the beginning of Feb (jamoluhrsen, 05:14:18)
   7. daniel is going to propose that we reduce even more from 3 SRs down to just 2. (jamoluhrsen, 05:17:12)
   8. ACTION: jamoluhrsen to reduce neon autorelease job to run once a week (jamoluhrsen, 05:19:00)
   
   
3. misc (jamoluhrsen, 05:19:12)
   1. abelur mentions the new global-jjb release will have the new tools to get cost estimates of our jenkins jobs. (jamoluhrsen, 05:22:51)
   2. there is news that controller is moving to an MRI project. (jamoluhrsen, 05:31:47)
   3. LuisGomez notes that we don't have an easy way to validate MRI projects before they release with CSIT. (jamoluhrsen, 05:33:08)
   4. as we keep moving towards more and more projects moving to MRI we will have more and more need to use CSIT to test unrleased versions of these projects. (jamoluhrsen, 05:35:12)
   5. currently the only way we are able to use CSIT to validate MRI projects is when they release and we run our multipatch job (jamoluhrsen, 05:35:36)

Action items

1. abelur to ping David to do the docs update
2. jamoluhrsen to reduce neon autorelease job to run once a week

Action items, by person

1. jamoluhrsen
   1. jamoluhrsen to reduce neon autorelease job to run once a week

People present (lines said)

1. jamoluhrsen (21)
2. odl_meetbot (4)