From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Andrea Bolognani <abologna@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Thomas Huth <thuth@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Cleber Rosa <crosa@redhat.com>, John Snow <jsnow@redhat.com>
Subject: Re: Python 3.5 EOL; when can require 3.6?
Date: Thu, 17 Sep 2020 17:35:45 +0100 [thread overview]
Message-ID: <20200917163545.GN1597829@redhat.com> (raw)
In-Reply-To: <b679e646f4dd8ebea753892c0cec27e54ba8f407.camel@redhat.com>
On Thu, Sep 17, 2020 at 06:07:00PM +0200, Andrea Bolognani wrote:
> On Thu, 2020-09-17 at 17:30 +0200, Markus Armbruster wrote:
> > Thomas Huth <thuth@redhat.com> writes:
> > > Sorry, I forgot to check Debian. If I got that right, Debian 9 still
> > > uses Python 3.5 by default. So I guess that means we can not deprecate
> > > Python 3.5 yet?
> >
> > Discussed before:
> >
> > Subject: Re: [PATCH] qapi: Fix code generation with Python 3.5
> > Date: Sat, 18 Jan 2020 07:54:18 +0100
> > Message-ID: <87lfq5s19h.fsf@dusky.pond.sub.org>
> > https://lists.nongnu.org/archive/html/qemu-devel/2020-01/msg03855.html
> >
> > Short version: Debian != Debian LTS. We support Debian until EOL, not
> > LTS. Debian 9 reached EOL in July.
>
> FWIW, this is the same policy the libvirt project follows, and we
> have formalized it at
>
> https://libvirt.org/platforms.html
>
> with Debian LTS being called out explicitly as not supported.
>
> It would be *fantastic* if we could keep the platform support policy
> used by QEMU and libvirt as aligned as reasonably possible.
The current QEMU policy was a copy+paste of the same policy I wrote for
libvirt originally, just adding OpenBSD/NetBSD.
I've just posted an update for QEMU which matches the latest libvirt
policy, again just adding the extra BSDs.
https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg06371.html
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 :|
next prev parent reply other threads:[~2020-09-17 16:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 7:43 Python 3.5 EOL; when can require 3.6? Markus Armbruster
2020-09-16 7:53 ` Philippe Mathieu-Daudé
2020-09-16 8:02 ` Thomas Huth
2020-09-16 8:16 ` Philippe Mathieu-Daudé
2020-09-16 13:53 ` Alex Bennée
2020-09-16 13:57 ` Daniel P. Berrangé
2020-09-17 14:53 ` Eduardo Habkost
2020-09-16 8:22 ` Andrea Bolognani
2020-09-16 15:09 ` Eduardo Habkost
2020-09-16 7:54 ` Thomas Huth
2020-09-16 8:33 ` Daniel P. Berrangé
2020-09-16 9:50 ` Thomas Huth
2020-09-16 9:54 ` Daniel P. Berrangé
2020-09-16 9:55 ` Thomas Huth
2020-09-16 8:31 ` Daniel P. Berrangé
2020-09-16 12:30 ` Peter Maydell
2020-09-16 13:30 ` Markus Armbruster
2020-09-16 14:00 ` Thomas Huth
2020-09-16 14:05 ` Daniel P. Berrangé
2020-09-16 14:57 ` John Snow
2020-09-17 14:10 ` Thomas Huth
2020-09-17 14:55 ` Daniel P. Berrangé
2020-09-17 15:24 ` Thomas Huth
2020-09-17 15:39 ` Daniel P. Berrangé
2020-09-17 15:41 ` Thomas Huth
2020-09-17 15:30 ` Markus Armbruster
2020-09-17 15:39 ` Thomas Huth
2020-09-17 15:42 ` Warner Losh
2020-09-17 16:07 ` Andrea Bolognani
2020-09-17 16:35 ` Daniel P. Berrangé [this message]
2020-09-17 17:02 ` Andrea Bolognani
2020-09-17 16:19 ` Eduardo Habkost
2020-09-17 16:33 ` Daniel P. Berrangé
2020-09-17 16:50 ` Eduardo Habkost
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=20200917163545.GN1597829@redhat.com \
--to=berrange@redhat.com \
--cc=abologna@redhat.com \
--cc=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
/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.