qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: 李强 <liq3ea@163.com>, "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: liq3ea@gmail.com, qemu-devel@nongnu.org,
	Markus Armbruster <armbru@redhat.com>,
	kraxel@redhat.com, pbonzini@redhat.com, lersek@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/3] fw_cfg: fix boot bootsplash and reboot-timeout error checking
Date: Wed, 21 Nov 2018 11:11:00 -0600	[thread overview]
Message-ID: <7fe10f10-d913-4060-9e17-7b3e2dff1ac9@redhat.com> (raw)
In-Reply-To: <169ff9e0.8b5b.16734530e0c.Coremail.liq3ea@163.com>

On 11/20/18 9:31 PM, 李强 wrote:

> 
> Nice, when 4.0 window open? I don't find the release planning.

https://wiki.qemu.org/Planning gives the overview, and 
https://wiki.qemu.org/Planning/3.1 gives the dates we are trying to hit 
for 3.1.

> Maybe my another fw_cfg patches can be merged:
> -->https://lists.gnu.org/archive/html/qemu-devel/2018-11/msg00004.html
> -->https://lists.gnu.org/archive/html/qemu-devel/2018-11/msg00005.html

Any new features have missed 3.1, especially since -rc2 has already been 
cut.  There is still room for bug fixes in -rc3, but the bar gets 
progressively higher (we are reluctant to take something that might 
destabilize the binaries without adequate time for testing), and while 
we want to avoid an -rc4, past history says we'll probably have one, 
although it will be as limited as possible.

> PS: I'm quite surprise the qemu's version up to 4 quickly(anyway, the 3.1 is just begin)...

Version numbers are somewhat arbitrary.  We recently switched to bumping 
the major version every year (it's arbitrary, after all), so 2019 will 
have 4.0, 4.1, and probably 4.2 (if we stick to a release every 4 
months) before 2020 starting with 5.0.  The change from 3.0 to 3.1 will, 
in reality, be about the same as the change from 3.1 to 4.0.  A better 
way to think of it is that both the old and new naming schemes are both 
arbitrary, but the new naming scheme has the benefit of not resulting in 
large minor numbers.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

      reply	other threads:[~2018-11-21 17:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 15:47 [Qemu-devel] [PATCH 0/3] fw_cfg: fix boot bootsplash and reboot-timeout error checking Li Qiang
2018-11-19 15:47 ` [Qemu-devel] [PATCH 1/3] fw_cfg: fix -boot bootsplash " Li Qiang
2018-11-20 19:30   ` Markus Armbruster
2018-11-19 15:47 ` [Qemu-devel] [PATCH 2/3] fw_cfg: fix -boot reboot-timeout " Li Qiang
2018-11-20 19:32   ` Markus Armbruster
2018-11-19 15:47 ` [Qemu-devel] [PATCH 3/3] fw_cfg: make qemu_extra_params_fw locally Li Qiang
2018-11-20 19:33   ` Markus Armbruster
2018-11-20 19:34 ` [Qemu-devel] [PATCH 0/3] fw_cfg: fix boot bootsplash and reboot-timeout error checking Markus Armbruster
2018-11-20 19:59   ` Philippe Mathieu-Daudé
2018-11-21  3:31     ` 李强
2018-11-21 17:11       ` Eric Blake [this message]

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=7fe10f10-d913-4060-9e17-7b3e2dff1ac9@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lersek@redhat.com \
    --cc=liq3ea@163.com \
    --cc=liq3ea@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --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).