From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: quintela@redhat.com, kvm-devel <kvm@vger.kernel.org>,
qemu-devel@nongnu.org,
"Daniel P . Berrange" <berrange@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Cleber Rosa" <crosa@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Bin Meng" <bin.meng@windriver.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"John Snow" <jsnow@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Erik Skultety" <eskultet@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Andrea Bolognani" <abologna@redhat.com>,
"Bin Meng" <bmeng.cn@gmail.com>
Subject: Re: KVM call for agenda for 2020-05-19
Date: Mon, 18 May 2020 18:21:53 +0200 [thread overview]
Message-ID: <133d4900-c852-f45d-ab19-a9253013fd20@redhat.com> (raw)
In-Reply-To: <87o8r24p2a.fsf@secure.mitica>
On 5/5/20 1:08 PM, Juan Quintela wrote:
>
>
> 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/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.
>
>
prev parent reply other threads:[~2020-05-18 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 11:08 KVM call for agenda for 2020-05-19 Juan Quintela
2020-05-18 16:21 ` Philippe Mathieu-Daudé [this message]
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=133d4900-c852-f45d-ab19-a9253013fd20@redhat.com \
--to=philmd@redhat.com \
--cc=abologna@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=bin.meng@windriver.com \
--cc=bmeng.cn@gmail.com \
--cc=crosa@redhat.com \
--cc=eskultet@redhat.com \
--cc=jsnow@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=marcandre.lureau@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).