Hi folks,

We held our regular design meeting today via Hangout. Summary of brief discussion:

3rd July 2019

1. [Rémi] 2019.07 release?

1. Should we do one? 2. Most people will be out for most of the month 3. Maybe worth it for the LITE group (depends on the number of patches). 4. Steve back from DebConf on the 28th, but… 5. Yes: releasing around the 18th

2. [Rémi] Debian buster is due soon

1. Basing the docker image on Buster? 2. No, wait for a little bit. Maybe 2019.08? 3. Staging is already running Buster, main v.l.o is still on Stretch but the lab team will want to upgrade soon 4. How long do we support stretch-backports? 5. Add buster-backports soon, as new uploads will hit Debian unstable (---> Bullseye). 6. Target 2019.08 at all three releases (stretch-backports, buster-backports, bullseye)

3. [Rémi] Recommendations about VACUUM ANALYZE

1. This should be run regularly (every day) on busy instances to clean up 2. Add a thing in the docs, test in the lab 3. See https://www.postgresql.org/docs/11/sql-vacuum.html for more info - does a VACUUM then ANALYZE without the old data. 4. Lets the DB self-optimise for performance

4. [Rémi] Using git submodule to include docker sources into lava sources 1. Still a separate repository 2. The exact commit hash used for the lava docker image is now known and reproducible. 1. This is the main reason 2. Using version.py on the last commit of the docker directory can also work. 3. See https://git.lavasoftware.org/lava/lava/merge_requests/637 4. Let's go with this instead of git submodule, it works fine

============================================================================

The LAVA design meeting is held weekly, every Wednesday at 13:00 to 14:00 UTC using Google Hangouts Meet: https://meet.google.com/qre-rgen-zwc Feel free to comment here or join us directly in the meeting.

Minutes from this and previous meetings are also stored in the LAVA wiki:

https://git.lavasoftware.org/lava/lava/wikis/design-meetings/index

Cheers,