From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, libvir-list@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/3] ui: remove deprecated UI frontends
Date: Wed, 8 Aug 2018 13:58:27 +0100 [thread overview]
Message-ID: <20180808125726.GA22936@redhat.com> (raw)
In-Reply-To: <20180808112409.wazgnksmsvhl4sa6@sirius.home.kraxel.org>
On Wed, Aug 08, 2018 at 01:24:09PM +0200, Gerd Hoffmann wrote:
> On Wed, Aug 08, 2018 at 11:49:27AM +0100, Daniel P. Berrangé wrote:
> > We deprecated GTK2 and SDL1.2 in the 2.12.0 release, so they are able to
> > be removed entirely in the 3.1.0 release. The min GTK3 version can also
> > be bumped up based the distros we aim to support.
>
> Yes for gtk2, finally the #ifdef mess is gone, yay!
>
> Not so sure for sdl1, that one was more controversial and sdl2
> regression fixes are still tickling in (although it seems we killed most
> of them meanwhile). Also due to sdl1 being a separate source file
> anyway the maintanance costs are not that high.
>
> Comments?
There were some regressions wrt SDL2, but I don't think there's any
major problems still missing. If there are new problems reported, we
still have the entire of the 3.1.0 dev cycle to address them before
the release which removes it.
Even if code is separate, it still has a maint cost in testing and impacts
any refactoring we do, such as that around keymap handling which is a
non-trivial cost for something that is increasingly unused, since we
default to SDL2 ABI for many releases now. At least GTK2 still had bug-fix
releases for any security problems or serious bugs, but SDL1 has received
no releases at all upstream since 2013
So I don't see any compelling reason to keep it alive given, and enough
downside given that it has been dead in its upstream community for years.
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:[~2018-08-08 12:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 10:49 [Qemu-devel] [PATCH 0/3] ui: remove deprecated UI frontends Daniel P. Berrangé
2018-08-08 10:49 ` [Qemu-devel] [PATCH 1/3] ui: remove support for GTK2 in favour of GTK3 Daniel P. Berrangé
2018-08-08 10:49 ` [Qemu-devel] [PATCH 2/3] ui: increase min required GTK3 version to 3.14.0 Daniel P. Berrangé
2018-08-08 10:49 ` [Qemu-devel] [PATCH 3/3] ui: remove support for SDL1.2 in favour of SDL2 Daniel P. Berrangé
2018-08-08 13:51 ` Peter Maydell
2018-08-08 13:55 ` Daniel P. Berrangé
2018-08-22 9:53 ` Daniel P. Berrangé
2018-08-08 11:24 ` [Qemu-devel] [PATCH 0/3] ui: remove deprecated UI frontends Gerd Hoffmann
2018-08-08 12:58 ` Daniel P. Berrangé [this message]
2018-08-21 7:46 ` Gerd Hoffmann
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=20180808125726.GA22936@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=libvir-list@redhat.com \
--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.