qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: seabios@seabios.org
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu 1.7 & seabios -- release planning
Date: Tue, 15 Oct 2013 12:04:05 +0200	[thread overview]
Message-ID: <1381831445.3709.58.camel@nilsson.home.kraxel.org> (raw)

  Hi,

It's probably going to be a bit tough this time.  We are pretty late in
the qemu 1.7 devel cycle, soft freeze today, and a big chunk of code
(ahci-tables-from qemu) which needs seabios support[1] is just about to
be pulled.

That leaves only two weeks (with kvm forum in the middle!) until qemu
1.7 hard freeze with -rc0 (2013-10-29), which should ideally have a
seabios update so it can be tested in the rc phase.

There are two more interface updates (pass pcimem64-start address + e820
entries for ram regions) which would be good to get in while being at
it.

seabios patches are ready for the most part and just waiting for the
qemu counterparts to be merged first.

The timing constrains suggest we should tightly align the releases, with
seabios releases being a bit earlier, i.e. something like this:

  (1) merge pending qemu patches
  (2) merge pending seabios patches
  (3) tag -rc0 seabios release [asap, no later than 2013-10-28]
  (4) merge seabios update into qemu
  (5) qemu hard freeze, -rc0 release with seabios update [2013-10-29]
  (6) seabios freeze in parallel with qemu hard freeze
  (7) apply seabios fixes if needed.
  (8) tag final seabios release [targeting qemu -rc2 or -rc3 date here]
  (9) merge seabios bugfix update into qemu

Qemu 1.7 schedule is here: http://wiki.qemu.org/Planning/1.7

Comments?

cheers,
  Gerd

[1] Strictly speaking it isn't absolutely required, but would be very
    good to have.

             reply	other threads:[~2013-10-15 10:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 10:04 Gerd Hoffmann [this message]
2013-10-15 12:40 ` [Qemu-devel] [SeaBIOS] qemu 1.7 & seabios -- release planning Kevin O'Connor
2013-10-29  9:15 ` 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=1381831445.3709.58.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).