16th January 2019

1. [Rémi] LAVA 2019.01 release
   1. When ?
   2. Maybe 24th January?
   3. Not sure how to do the functional release tests
   4. What should be in?
   5. Existing MRs:
   6. !336 (merged) Milosz testing
   7. !333 (merged) - merge, looks good
   8. !331 (merged) - merge, definitely needed
   9. !328 (merged) - looks good
   10. !324 (merged) - needs review
   11. !323 (merged), !321 (merged) will wait
   12. !309 (merged) - check and review
   13. !302 (merged) - review
   14. !295 (merged) will wait for discussion
   15. !294 (merged) needs more work
2. [Rémi] BKK presentation?
   1. lavafed/meta-lava?
      1. Yes please!
      2. LAVA community enabled testing
   2. LAVA user forum
      1. Already requested
   3. Bootloader testing (with Loïc Poulain)
      1. Yes!
3. [Rémi] Inviting community to the design meeting?
   1. Make it public by default.
      1. How? Just make the link public? Seems to work OK
      2. Mail to lava-devel each week with summary of the minutes, with a link to the HO for the meeting itself [Steve]
      3. Mail to -announce describing this [Steve]
      4. If we ever overflow what hangouts will deal with, worry about it then
   2. If we ever need private meetings, we can have those as needed
4. [Stevan] Access rights improvement and decoupling scheduler from the frontend
   1. LSS-372
   2. LSS-375
      1. Open ticket in gitlab, send mail to lava-devel list with the description and link to the ticket