From: Markus Armbruster <armbru@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Cornelia Huck" <cohuck@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Olaf Hering" <olaf@aepfle.de>, "Fam Zheng" <famz@redhat.com>,
qemu-trivial@nongnu.org,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"open list:All patches CC here" <qemu-devel@nongnu.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH v1] configure: require glib-2.24
Date: Thu, 19 Apr 2018 09:19:28 +0200 [thread overview]
Message-ID: <87sh7rvf27.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20180418125545.GN27579@redhat.com> ("Daniel P. Berrangé"'s message of "Wed, 18 Apr 2018 13:55:45 +0100")
Daniel P. Berrangé <berrange@redhat.com> writes:
> On Wed, Apr 18, 2018 at 02:45:38PM +0200, Cornelia Huck wrote:
>
>> Are we ready to give up support for whatever distro is still on 2.22?
>> (If yes, can we bump to an even newer glib version?) Or should we
>> rather solve this by adding a g_realloc_n implementation for that case?
>
> Version 2.22 was released in Sep 2009, so coming up for 9 years old now.
>
> At some point we should to declare that platforms shipping >= NNN year
> old versions of software are not a desirable target for QEMU. What is
> our desired NNN value - 9 years feels awfully long to me.
>
> For libvirt we recently decided to become more aggressive[1] in culling old
> distros as supportable targets, declaring we'll only support non-EOL
> distros (for short life distros), or for long life distros (RHEL, LTS, etc)
> the most recent version, and the recent minus-1 for 2 years overlap.
>
> Should we formalize similar guidelines for QEMU to give developers a
> guide for when it is reasonable to increase the min required version of
> any 3rd party library ? glib is a mandatory dep, but we've countless
> other optional libraries we might wish to increase min versions for too,
> and no guide on when it is reasonable todo so.
Yes, please.
>
> Regards,
> Daniel
>
> [1] https://libvirt.org/platforms.html
This policy looks sensible to me
next prev parent reply other threads:[~2018-04-19 7:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 12:38 [Qemu-trivial] [PATCH v1] configure: require glib-2.24 Olaf Hering
2018-04-18 12:45 ` [Qemu-trivial] [Qemu-devel] " Cornelia Huck
2018-04-18 12:55 ` Daniel P. Berrangé
2018-04-18 14:41 ` Cornelia Huck
2018-04-18 14:43 ` Daniel P. Berrangé
2018-04-19 7:19 ` Markus Armbruster [this message]
2018-04-19 7:30 ` Olaf Hering
2018-04-19 7:59 ` Daniel P. Berrangé
2018-04-19 8:54 ` Peter Maydell
2018-04-19 9:01 ` Kamil Rytarowski
2018-04-19 9:20 ` Gerd Hoffmann
2018-04-19 9:23 ` Daniel P. Berrangé
2018-04-18 14:45 ` Olaf Hering
2018-04-18 12:47 ` Daniel P. Berrangé
2018-04-18 13:00 ` Olaf Hering
2018-04-18 13:29 ` Peter Maydell
2018-04-18 14:44 ` Daniel P. Berrangé
2018-04-26 8:17 ` Peter Maydell
2018-04-26 9:19 ` Thomas Huth
2018-04-26 9:54 ` Peter Maydell
2018-04-26 11:52 ` Paolo Bonzini
2018-04-26 12:08 ` Olaf Hering
2018-04-26 12:10 ` Daniel P. Berrangé
2018-04-26 12:11 ` Olaf Hering
2018-04-26 12:39 ` Paolo Bonzini
2018-04-26 12:42 ` Paolo Bonzini
2018-04-26 12:42 ` Olaf Hering
2018-04-26 12:12 ` Peter Maydell
2018-04-18 13:34 ` Eric Blake
2018-04-18 12:53 ` no-reply
2018-04-18 13:04 ` Olaf Hering
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=87sh7rvf27.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=kraxel@redhat.com \
--cc=olaf@aepfle.de \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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.