[Releasing] Removal of engin.io from Qt 5.7

Hausmann Simon Simon.Hausmann at theqtcompany.com
Fri Jan 29 09:01:36 CET 2016


Just to clarify:

What Ossi is proposing is - starting with Qt 5.6.0 - to stop including qtenginio in the binary packages.

In contrast to that Tuukka's proposal is to include the binaries in Qt 5.6.0 but _stop_ including them in subsequent 5.6.x releases.

Which way should we go?


P.S.: I'm in favor of Ossi's suggestion.

From: Releasing <releasing-bounces at qt-project.org> on behalf of Oswald Buddenhagen <oswald.buddenhagen at theqtcompany.com>
Sent: Thursday, January 28, 2016 12:17
To: Turunen Tuukka
Cc: releasing at qt-project.org
Subject: Re: [Releasing] Removal of engin.io from Qt 5.7

On Wed, Jan 27, 2016 at 10:04:57PM +0000, Turunen Tuukka wrote:
> From: Nowacki Jedrzej
> > What is the idea for Qt5.6 which is LTS? Does it make sense to include
> > QtEnginio there?
> >
> As decided earlier it is included in the Qt 5.6.0 packages, but marked
> as deprecated. As such, it is not subject to the LTS promise. It can
> be dropped out from some patch release of Qt 5.6.x, if it not longer
> needed.
i'd approach this differently:
we already concluded that we cannot *really* remove any modules
(specifically, webkit and quick1 so far) before qt6, as "just use the
old versions if you still need them" has already proven to be
spectacularly unworkable. the consequence is that these modules will be
still available in the installer, but only as sources and with a big fat
warning (or something).
with that in mind, it may be reasonable to "remove" enginio right away
as well, given that discouraging people from using it is acutely urgent.
Releasing mailing list
Releasing at qt-project.org

More information about the Releasing mailing list