From: Gerd Hoffmann <kraxel@redhat.com>
To: seabios <seabios@seabios.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] seabios release planning
Date: Fri, 29 Nov 2013 16:13:35 +0100 [thread overview]
Message-ID: <1385738015.23450.32.camel@nilsson.home.kraxel.org> (raw)
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.
Pending patches:
* my ahci and pci patches sent this week.
* anything else?
How we wanna call the baby? 1.7.4? 1.8.0?
cheers,
Gerd
next reply other threads:[~2013-11-29 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 15:13 Gerd Hoffmann [this message]
2013-11-29 18:43 ` [Qemu-devel] [SeaBIOS] seabios release planning Kevin O'Connor
2013-12-19 12:12 ` 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=1385738015.23450.32.camel@nilsson.home.kraxel.org \
--to=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).