From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>,
qemu list <qemu-devel@nongnu.org>
Subject: [Qemu-devel] KVM call for agenda 2014-04-01
Date: Tue, 01 Apr 2014 17:34:27 +0200 [thread overview]
Message-ID: <87vbutawsc.fsf@elfo.mitica> (raw)
2014-04-01
----------
- port of virtio to vmstate
* problem are lists (virtio-net/virtio-serial)
Relaese process
- Delay release for a few days to be able to test the tarball.
- Michael Rooth do the realese
- Stefan get used as "realse manager backup"
- Dates agreed:
2014-04-01 Tag v2.0.0-rc1
2014-04-08 Tag v2.0.0
Conference call
- we sent calls for agenda one day before, 2 weeks before, 1 week before
and not a lot of calls. What should we do to improve?
Plan is to sent: one week before and a reminder the day before
- Qemu is better modularized nowadays, and less changes involve the whole tree
- If you have any suggestion for the conference call told me.
Stefan virtio property patches
next reply other threads:[~2014-04-01 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 15:34 Juan Quintela [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-01 15:34 [Qemu-devel] KVM call for agenda 2014-04-01 Juan Quintela
2014-04-01 17:06 ` Peter Maydell
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=87vbutawsc.fsf@elfo.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 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).