All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergio.durigan@canonical.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org,  qemu-stable@nongnu.org
Subject: Re: [ANNOUNCE] QEMU 8.2.6 Stable released
Date: Tue, 27 Aug 2024 14:48:29 -0400	[thread overview]
Message-ID: <87ikvlrede.fsf@canonical.com> (raw)
In-Reply-To: <1721203806.547734.831464.nullmailer@tls.msk.ru> (Michael Tokarev's message of "Wed, 17 Jul 2024 11:10:06 +0300")

On Wednesday, July 17 2024, Michael Tokarev wrote:

> Hi everyone,

Hey Michael,

> The QEMU v8.2.6 stable release is now available.
>
> You can grab the tarball from our download page here:
>
>   https://www.qemu.org/download/#source
>
>   https://download.qemu.org/qemu-8.2.6.tar.xz
>   https://download.qemu.org/qemu-8.2.6.tar.xz.sig (signature)
>
> v8.2.6 is now tagged in the official qemu.git repository, and the
> stable-8.2 branch has been updated accordingly:
>
>   https://gitlab.com/qemu-project/qemu/-/commits/stable-8.2
>
> There are 23 changes since the previous v8.2.5 release, including
> a fix for CVE-2024-4467 (qemu-img info command lack of input validation).
> This is supposed to be the last release in 8.2.x series.
>
> Thank you everyone who has been involved and helped with the stable series!

We talked on IRC but I thought I'd drop this email and make it official.
Ubuntu 24.04 Noble ships QEMU 8.2.x and it would be great if the
stable-8.2 series were to be maintained for a longer period of time.  I
can try helping with review/backporting as time permits.

Thanks for working on this.

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14


      reply	other threads:[~2024-08-27 19:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-17  8:10 [ANNOUNCE] QEMU 8.2.6 Stable released Michael Tokarev
2024-08-27 18:48 ` Sergio Durigan Junior [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=87ikvlrede.fsf@canonical.com \
    --to=sergio.durigan@canonical.com \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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.