All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: qemu 10.0 release and the next debian stable release (trixie)
Date: Tue, 18 Feb 2025 09:36:25 +0000	[thread overview]
Message-ID: <Z7RUmX-_Lqy6_CGw@redhat.com> (raw)
In-Reply-To: <138bb61b-d7a4-47e0-b746-f1d3a14c6dc8@tls.msk.ru>

On Tue, Feb 18, 2025 at 11:50:57AM +0300, Michael Tokarev wrote:
> Hi!
> 
> It so happened that current schedule for debian and qemu clashes with
> each other in a fun way.  2025-04-15 is the date planned for qemu 10.0
> release (if no rc4 is needed), and is it the date of debian 13.0 trixe
> freeze.
> 
> Can we move the qemu release date a little bit earlier, so I'll have
> a chance to upload qemu 10.0 to debian trixie?

That's just the Debian soft freeze date IIUC[1], so isn't it possible to
ship the -rc3 release at the the time of soft freeze and then do an update
to the final release which would arrive before hard freeze a month later ? 


With regards,
Daniel

[1] https://release.debian.org/
-- 
|: 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-02-18  9:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18  8:50 qemu 10.0 release and the next debian stable release (trixie) Michael Tokarev
2025-02-18  9:36 ` Daniel P. Berrangé [this message]
2025-02-18 10:29   ` Michael Tokarev

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=Z7RUmX-_Lqy6_CGw@redhat.com \
    --to=berrange@redhat.com \
    --cc=mjt@tls.msk.ru \
    --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.