From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: The OpenBIOS Mailinglist <openbios@openbios.org>
Subject: Re: [Qemu-devel] How are we looking for a release?
Date: Fri, 27 Feb 2009 15:01:17 -0600 [thread overview]
Message-ID: <49A8549D.9010703@codemonkey.ws> (raw)
In-Reply-To: <f43fc5580902271228h17cb31f2x575d086e8642bf47@mail.gmail.com>
Blue Swirl wrote:
> On 2/27/09, Anthony Liguori <anthony@codemonkey.ws> wrote:
>
>> Hi,
>>
>> I wanted to see how we look from a release perspective. For x86, I think
>> things are looking pretty good. There are a couple outstanding patches that
>> need more review (like the CVE fix) but I think we'll be ready in a few
>> days.
>>
>> How are the other architectures looking? Are there any major bug fixes
>> people are working on? PPC is now fully converted to OpenBIOS, right?
>>
>
> Yes, except for PREP.
>
Is anyone working on converting PREP? Any ETA?
> There are recent patches to make PPC64 work that should be committed
> in the coming days. That would be a nice addition but not critical.
>
> We have also discussed about making also an OpenBIOS (1.0) release,
> the previous release candidate (1.0RC1) is more than year old. It
> would be great to release Qemu with 1.0 OpenBIOS.
>
It would be great to have a 1.0 release for our release, but do you have
an ETA on when that would be? It would be very good to get out a QEMU
release within the next few days to match up with the upcoming set of
distro releases.
And if things are moving quickly, we certainly have the ability to do
releases every 3 months instead of every 6.
Regards,
Anthony Liguori
> Overall, there should be an update of the OpenBIOS images, otherwise
> Sparc32 and I think PPC32 are ready. Sparc64 will not be without major
> miracles in any case. PPC64 case may be interesting.
>
>
>
next prev parent reply other threads:[~2009-02-27 21:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 17:37 [Qemu-devel] How are we looking for a release? Anthony Liguori
2009-02-27 18:37 ` Andreas Färber
2009-02-27 18:55 ` Anthony Liguori
2009-02-27 19:20 ` malc
2009-02-27 19:38 ` Anthony Liguori
2009-02-27 21:55 ` malc
2009-03-01 17:41 ` Andreas Färber
2009-03-02 10:15 ` Alexander Graf
2009-02-27 20:28 ` Blue Swirl
2009-02-27 21:01 ` Anthony Liguori [this message]
2009-02-27 21:23 ` [OpenBIOS] " Blue Swirl
2009-02-27 21:28 ` Stefan Reinauer
2009-02-28 20:32 ` Jamie Lokier
-- strict thread matches above, loose matches on Subject: below --
2009-02-27 17:36 Anthony Liguori
[not found] ` <CC23DCE2-743F-4167-9C70-33809CC972F9@hotmail.com>
2009-02-27 18:36 ` C.W. Betts
2009-02-28 4:47 ` Edgar E. Iglesias
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=49A8549D.9010703@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=openbios@openbios.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).