From: Juan Quintela <quintela@redhat.com>
To: kvm-devel <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: KVM call for 2016-06-16
Date: Mon, 15 Jun 2020 11:34:32 +0200 [thread overview]
Message-ID: <87wo48n047.fsf@secure.mitica> (raw)
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/qemu-devel@nongnu.org/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
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.
next reply other threads:[~2020-06-15 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 9:34 Juan Quintela [this message]
2020-06-15 9:45 ` KVM call for 2016-06-16 Philippe Mathieu-Daudé
2020-06-15 10:28 ` Juan Quintela
2020-06-15 10:28 ` Juan Quintela
2020-06-16 8:48 ` Juan Quintela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wo48n047.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.