qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin O'Connor <kevin@koconnor.net>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: seabios <seabios@seabios.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [SeaBIOS] seabios release planning
Date: Fri, 29 Nov 2013 13:43:54 -0500	[thread overview]
Message-ID: <20131129184354.GA9757@morn.localdomain> (raw)
In-Reply-To: <1385738015.23450.32.camel@nilsson.home.kraxel.org>

On Fri, Nov 29, 2013 at 04:13:35PM +0100, Gerd Hoffmann wrote:
>   Hi,
> 
> qemu 1.7 is almost out of the door.  I want update seabios early in the
> 1.8 devel cycle.  Time to do resume the release planning since we've
> scratched the idea to do a last-minute bios update for 1.7.
> 
> I'd like to see a seabios release from the master branch in december.
> Ideally we'll put a prerelease into qemu before the final release so we
> get some testing.  We could either explicitly tag a release candidate or
> just grab a snapshot for that.
> 
> Commit pending patches, enter seabios freeze, prepare seabios update for
> qemu can be done next week I think.  Then have 2-3 weeks freeze period,
> tag final release before xmas.  In case something doesn't go as planned
> early january.

So that would look like a SeaBIOS feature freeze on Dec 6th and target
release date of Dec 20th.  Works for me.

> Pending patches:
>  * my ahci and pci patches sent this week.
>  * anything else?
> 
> How we wanna call the baby? 1.7.4? 1.8.0?

I'd say v1.7.4.

-Kevin

  reply	other threads:[~2013-11-29 18:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29 15:13 [Qemu-devel] seabios release planning Gerd Hoffmann
2013-11-29 18:43 ` Kevin O'Connor [this message]
2013-12-19 12:12   ` [Qemu-devel] [SeaBIOS] " Gerd Hoffmann

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=20131129184354.GA9757@morn.localdomain \
    --to=kevin@koconnor.net \
    --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).