KVM call for 2016-06-16
Hi
Please, send any topic that you are interested in covering. There is already a topic from last call:
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
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
(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.
Hi Juan,
Quoted 5 lines · Juan Quintela
Hi
Please, send any topic that you are interested in covering. There is already a topic from last call:
This topic was already discussed in the last call :)
Quoted 56 lines
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.htmlAt 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
(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.
Quoted 10 lines · Philippe Mathieu-Daudé
Hi Juan,
Quoted 5 lines · Juan Quintela
Hi
Please, send any topic that you are interested in covering. There is already a topic from last call:
This topic was already discussed in the last call :)
Sorry.
My understanding from last call was that we wanted to discuss it with more people from more organizations.
Later, Juan.
Quoted 1 line · Juan Quintela
Hi
Hi
As there are no topics, this calls gets cancelled.
Happy hacking.
Later, Juan.
Quoted 57 lines
Please, send any topic that you are interested in covering. There is already a topic from last call:
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.htmlAt 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
(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.