All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Michael Roth <michael.roth@amd.com>
Cc: qemu-devel@nongnu.org, Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [ANNOUNCE] QEMU 10.2.0-rc1 is now available
Date: Wed, 3 Dec 2025 10:17:16 +0000	[thread overview]
Message-ID: <aTAOLP0m8HN_Iw84@redhat.com> (raw)
In-Reply-To: <176359557511.1845377.6752982148248088074@amd.com>

On Wed, Nov 19, 2025 at 05:39:35PM -0600, Michael Roth wrote:
> Hello,
> 
> On behalf of the QEMU Team, I'd like to announce the availability of the
> first+second release candidate for the QEMU 10.2 release (there was no
> rc0 published this time around). This release is meant for testing purposes
> and should not be used in a production environment.
> 
>   http://download.qemu.org/qemu-10.2.0-rc1.tar.xz
>   http://download.qemu.org/qemu-10.2.0-rc1.tar.xz.sig
> 
> You can help improve the quality of the QEMU 10.2 release by testing this
> release and reporting bugs using our GitLab issue tracker:
> 
>   https://gitlab.com/qemu-project/qemu/-/milestones/17
> 
> The release plan, as well a documented known issues for release
> candidates, are available at:
> 
>   http://wiki.qemu.org/Planning/10.2

Is our release schedule still accurate ?

rc2 was targetted at Nov 25th, but in git I see rc2 tagged yesterday
which is when rc3 was scheduled for tagging.

Are we going to go for another -rc next Tuesday, or straight from
rc2 to the release ?

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2025-12-03 10:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19 23:39 [ANNOUNCE] QEMU 10.2.0-rc1 is now available Michael Roth
2025-12-03 10:17 ` Daniel P. Berrangé [this message]
2025-12-06 13:27   ` 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=aTAOLP0m8HN_Iw84@redhat.com \
    --to=berrange@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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.