From: Blue Swirl <blauwirbel@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [FYI] Soft feature freeze for 1.0 is 10/15 (three weeks away)
Date: Sun, 25 Sep 2011 17:31:53 +0000 [thread overview]
Message-ID: <CAAu8pHuoP2hpMOBh91DTG_SS5jtwLVgWiTJqnb14kS+EJmFhXw@mail.gmail.com> (raw)
In-Reply-To: <4E7F5B62.1090307@redhat.com>
On Sun, Sep 25, 2011 at 4:48 PM, Avi Kivity <avi@redhat.com> wrote:
> On 09/25/2011 07:36 PM, Blue Swirl wrote:
>>
>> On Sun, Sep 25, 2011 at 2:10 PM, Avi Kivity<avi@redhat.com> wrote:
>> > On 09/24/2011 11:05 AM, Blue Swirl wrote:
>> >>
>> >> On Thu, Sep 22, 2011 at 12:34 AM, Anthony
>> >> Liguori<anthony@codemonkey.ws>
>> >> wrote:
>> >> > Consider this a friendly reminder that we're only three weeks
>> >> away from
>> >> > the
>> >> > soft feature freeze for 1.0. I've written a wiki page about my
>> >> > expectations
>> >> > for the soft feature freeze. It's inlined here for easier
>> >> commenting.
>> >>
>> >> I think the freezes and the release should be delayed until the memory
>> >> API conversion is finished, deliberately shipping semi-broken code
>> >> just to satisfy schedules does not benefit anyone but the schedule
>> >> creator. It looks to me that converting all buses and devices might be
>> >> finished by the deadline but it may as well take a bit more until
>> >> everything works again.
>> >>
>> >
>> > There is a difference between "incomplete conversion" and "semi-broken
>> > code". Any breakage should be fixed promptly, but after some freeze
>> > date
>> > (not sure if this is the one proposed), additional conversions would be
>> > pushed to 1.1.
>>
>> Well, there's PPC VGA which is semi-broken by the incomplete conversion.
>
> Please point out a test case and I'll try to fix it.
Run qemu-system-ppc without any arguments. There is a black bar
(because of vga.chain4), it shouldn't be there.
next prev parent reply other threads:[~2011-09-25 17:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 0:34 [Qemu-devel] [FYI] Soft feature freeze for 1.0 is 10/15 (three weeks away) Anthony Liguori
2011-09-24 8:05 ` Blue Swirl
2011-09-25 14:10 ` Avi Kivity
2011-09-25 16:36 ` Blue Swirl
2011-09-25 16:48 ` Avi Kivity
2011-09-25 17:31 ` Blue Swirl [this message]
2011-09-26 10:08 ` Avi Kivity
2011-09-26 10:10 ` Avi Kivity
2011-09-26 17:15 ` Blue Swirl
2011-09-26 17:18 ` Avi Kivity
2011-09-26 17:20 ` Blue Swirl
2011-09-26 17:24 ` Avi Kivity
2011-09-26 18:07 ` Blue Swirl
2011-09-27 8:33 ` Avi Kivity
2011-09-27 8:57 ` Avi Kivity
2011-09-27 16:39 ` Blue Swirl
2011-09-27 16:44 ` Avi Kivity
2011-09-27 19:19 ` Blue Swirl
2011-09-28 21:21 ` Alexander Graf
2011-09-29 19:28 ` Blue Swirl
2011-09-29 21:19 ` Alexander Graf
2011-09-25 19:50 ` Anthony Liguori
2011-09-30 3:21 ` Stefan Berger
2011-09-30 12:59 ` Anthony Liguori
2011-09-30 14:05 ` Stefan Berger
2011-10-10 12:14 ` Max Filippov
2011-09-24 21:56 Anthony Liguori
2011-09-25 16:28 ` Blue Swirl
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=CAAu8pHuoP2hpMOBh91DTG_SS5jtwLVgWiTJqnb14kS+EJmFhXw@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=avi@redhat.com \
--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.