All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Liu, Yi L" <yi.l.liu@intel.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	Jason Wang <jasowang@redhat.com>,
	Michael Roth <mdroth@linux.vnet.ibm.com>,
	"mst@redhat.com" <mst@redhat.com>
Subject: Re: about QEMU release schedule
Date: Fri, 6 Dec 2019 15:24:46 +0000	[thread overview]
Message-ID: <12B7DFF3-8414-4C26-97BD-DDF772D7433A@intel.com> (raw)
In-Reply-To: <CAFEAcA_A814+1_vvD+QO=cDeiWEXdUJyZgjuBeU2RTXaHYCh+A@mail.gmail.com>


>> On Dec 6, 2019, at 17:57, Peter Maydell <peter.maydell@linaro.org> wrote:
>> 
>> On Fri, 6 Dec 2019 at 04:00, Liu, Yi L <yi.l.liu@intel.com> wrote:
>> Hi Peter,
>> I’m wondering what’s the rule of QEMU version naming and release.
>> I noticed there is a v3.1.1.1 released after v4.1.0 was released.
> 
> Any reason for not just asking this on the public lists?

No, I should have cced mailing list, thus other people would learn it as well. 

>> Also, I’d like to query the release plan in 2020. What version would it
>> be in 2020-July?
> 
> For many years we've done major releases three times
> a year, in April, August and December (roughly).
> Starting from 4.0, we switched to a naming convention where
> the major number just increments once a year. So 2019's
> releases are 4.0, 4.1 and 4.2; 2020's will be 5.0, 5.1
> and 5.2, and so on.
> 
> Further releases on stable branches (eg 4.0.1, etc) are
> not handled by me -- they're done by Mike Roth. I don't
> know what the usual pattern is for those or how many
> branches back we do updates for.

Thanks a lot for the sharing. 

Regards,
Yi Liu

       reply	other threads:[~2019-12-06 16:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A2975661238FB949B60364EF0F2C25743A12875B@SHSMSX104.ccr.corp.intel.com>
     [not found] ` <CAFEAcA_A814+1_vvD+QO=cDeiWEXdUJyZgjuBeU2RTXaHYCh+A@mail.gmail.com>
2019-12-06 15:24   ` Liu, Yi L [this message]
2019-12-06 15:36     ` about QEMU release schedule Michael Roth

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=12B7DFF3-8414-4C26-97BD-DDF772D7433A@intel.com \
    --to=yi.l.liu@intel.com \
    --cc=jasowang@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.