Skip to contentSkip to conversation

KVM call for agenda for 2020-05-19

DISCUSSION Juan Quintela 2 participants 2 messages May 5, 2020 – May 18, 2020 KVM

lore
Share & tools
lore
#0 lore raw

Hi

Please, send any topic that you are interested in covering.

At the end of Monday I will send an email with the agenda or the cancellation of the call, so hurry up.

After discussions on the QEMU Summit, we are going to have always open a KVM call where you can add topics.

Call details:

By popular demand, a google calendar public entry with it

https://www.google.com/calendar/embed?src=dG9iMXRqcXAzN3Y4ZXZwNzRoMHE4a3BqcXNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ

(Let me know if you have any problems with the calendar entry. I just gave up about getting right at the same time CEST, CET, EDT and DST).

If you need phone number details, contact me privately

Thanks, Juan.

#1 lore raw
Quoted 5 lines · Juan Quintela

Hi

Please, send any topic that you are interested in covering.

Last minute suggestion after recent IRC chat with Alex Bennée and Thomas Huth:

"Move some of the build/CI infrastructure to GitLab."

Pro/Con?

- GitLab does not offer s390x/ppc64el => keep Travis for these?

How to coordinate efforts?

What we want to improve? Priorities?

Who can do which task / is motivated.

What has bugged us recently:
- Cross-build images (currently rebuilt all the time on Shippable)

Long term interests:

- Collect quality metrics
. build time
. test duration
. performances
. binary size
. runtime memory used

- Collect code coverage

Note, this is orthogonal to the "Gating CI" task Cleber is working on:
https://www.mail-archive.com/[email protected]/msg688150.html

Quoted 21 lines

At the end of Monday I will send an email with the agenda or the cancellation of the call, so hurry up.

After discussions on the QEMU Summit, we are going to have always open a KVM call where you can add topics.

Call details:

By popular demand, a google calendar public entry with it

https://www.google.com/calendar/embed?src=dG9iMXRqcXAzN3Y4ZXZwNzRoMHE4a3BqcXNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ

(Let me know if you have any problems with the calendar entry. I just gave up about getting right at the same time CEST, CET, EDT and DST).

If you need phone number details, contact me privately

Thanks, Juan.