Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • lava lava
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 94
    • Issues 94
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 45
    • Merge requests 45
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lava
  • lavalava
  • Wiki
  • Design meetings
  • 2019
  • 20190116

Last edited by Rémi Duraffort Apr 17, 2019
Page history

20190116

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 - needs review
    11. !323 (merged), !321 (merged) will wait
    12. !309 - check and review
    13. !302 - review
    14. !295 will wait for discussion
    15. !294 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
Clone repository
  • ci
  • design meetings
  • design meetings
    • 2019
      • 20190116
      • 20190123
      • 20190130
      • 20190206
      • 20190213
      • 20190220
      • 20190227
      • 20190306
      • 20190313
      • 20190320
      • 20190327
      • 20190417
      • 20190424
View All Pages