From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next
Date: Thu, 5 Nov 2015 15:01:44 +0100 [thread overview]
Message-ID: <563B6148.8030602@redhat.com> (raw)
In-Reply-To: <CAFEAcA-_1zfTM7XMudB83E9snaHU7C5x1MTN8SwMmo6MXyobUw@mail.gmail.com>
On 05/11/2015 14:44, Peter Maydell wrote:
> On 5 November 2015 at 13:23, Christian Borntraeger
> <borntraeger@de.ibm.com> wrote:
>> Maybe we should try to aim for a 3 month cadence for QEMU to reduce the
>> pain of missing soft/hard freeze. -> maybe a topic for the next QEMU
>> summit?
>
> We used to have 3 month releases, but I think we found that these
> were too short: If you have about a month hardfreeze and a month
> softfreeze then you only have a month of open feature development,
> which seems pretty short to me.
It's short unless you assume that development goes on in private
maintainer trees during hard freeze. It's always happened at least for
the block layer, and probably for everything else. About 400 commits in
2.5 were authored before the 2.4 release.
The main issue is that shorter cycles may mean fewer and bigger pull
requests. It also means more awareness of conflicts is needed. We
definitely lack the continuous integration infrastructure that is needed
for that.
Paolo
next prev parent reply other threads:[~2015-11-05 14:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 11:42 [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next Peter Maydell
2015-11-05 11:49 ` Paolo Bonzini
2015-11-05 12:13 ` Gerd Hoffmann
2015-11-05 12:32 ` Peter Maydell
2015-11-05 13:23 ` Christian Borntraeger
2015-11-05 13:44 ` Peter Maydell
2015-11-05 13:46 ` Christian Borntraeger
2015-11-05 14:01 ` Paolo Bonzini [this message]
2015-11-05 14:30 ` Peter Maydell
2015-11-05 14:52 ` Peter Maydell
2015-11-05 15:03 ` Paolo Bonzini
2015-11-05 14:58 ` Paolo Bonzini
2015-11-05 18:56 ` Peter Maydell
2015-11-05 13:48 ` Laszlo Ersek
2015-11-05 15:52 ` Alex Bennée
2015-11-05 17:05 ` Laszlo Ersek
2015-11-05 17:09 ` Paolo Bonzini
2015-11-05 14:42 ` Gerd Hoffmann
2015-11-05 14:45 ` Peter Maydell
2015-11-05 14:58 ` Gerd Hoffmann
2015-11-05 15:11 ` Peter Maydell
2015-11-05 17:15 ` Laszlo Ersek
2015-11-05 18:13 ` Cornelia Huck
2015-11-05 18:51 ` Laszlo Ersek
2015-11-06 16:34 ` Alex Bennée
2015-11-06 16:43 ` 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=563B6148.8030602@redhat.com \
--to=pbonzini@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.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).