From: Kevin O'Connor <kevin@koconnor.net>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Gabriel L. Somlo" <gsomlo@gmail.com>,
seabios <seabios@seabios.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [SeaBIOS] seabios release?
Date: Thu, 8 May 2014 18:47:48 -0400 [thread overview]
Message-ID: <20140508224748.GA27295@morn.localdomain> (raw)
In-Reply-To: <1399458815.7238.22.camel@nilsson.home.kraxel.org>
On Wed, May 07, 2014 at 12:33:35PM +0200, Gerd Hoffmann wrote:
> On Mi, 2014-04-23 at 16:41 +0200, Gerd Hoffmann wrote:
> > Hi,
> >
> > I think it's time to start planning the next seabios release. First,
> > because a bunch of changes have piled up in master. And second, because
> > of the smbios changes. They are a step forward in making seabios less
> > dependent on qemu internals and I want have that in qemu soonish.
> >
> > So, how about this plan:
> >
> > (1) merge smbios patches in qemu (patchset is close to final now).
> > (2) merge smbios patch in seabios
>
> We are here now ...
>
> > (3) start freeze
> > (4) tag release candidate (early may is realistic for that I think).
>
> ... so it's time kick freeze + release candidate I guess ;)
>
> Are there any pending patches for the next release which should better
> make it into the release candidate?
I just sent a few fixes to the mailing list (xhci msleep, romlayout.o
rebuild, int 1589 fix). I think these should go into the final
release. Unless there are comments on the above patches I'll push
them on Monday.
I think we can then also start the feature freeze on Monday.
-Kevin
next prev parent reply other threads:[~2014-05-08 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1398264092.26634.96.camel@nilsson.home.kraxel.org>
2014-05-07 10:33 ` [Qemu-devel] [SeaBIOS] seabios release? Gerd Hoffmann
2014-05-08 22:47 ` Kevin O'Connor [this message]
2014-05-09 14:12 ` Gerd Hoffmann
2014-05-13 14:35 ` Kevin O'Connor
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=20140508224748.GA27295@morn.localdomain \
--to=kevin@koconnor.net \
--cc=gsomlo@gmail.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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).