[Development] Future of Qt Quick 1 in Qt 5

Thiago Macieira thiago.macieira at intel.com
Sat May 9 15:47:45 CEST 2015

On Saturday 09 May 2015 09:31:29 Pau Garcia i Quiles wrote:
> On Sat, May 9, 2015 at 6:34 AM, Turunen Tuukka <
> tuukka.turunen at theqtcompany.com> wrote:
> The thing is that since the beginning of Qt 5 we have been constantly
> > adding things and not removing the parts that are less used (and
> > deprecated). Even though one might think it takes very little effort to
> > keep things around, the aggregate effort is significant.
> > 
> > There are many great new things and improvements we could bring into Qt,
> > but now a lot of time goes into keeping old parts afloat. If someone needs
> > to use an old module, why not do it with a Qt version that supports it?
> > Same goes to platforms and compilers - it is not feasible to properly
> > support all upcoming and old versions.
> Break backwards compatibility promise, remove hard-to-maintain modules
> which have an alternative, introduce some fundamental code changes... It
> seems to me Qt 6 is perfectly justified :-?

Why do people read "remove" as in "you need to stop using it now"?

When we're saying "remove", we meant only that it's no longer included in the 
convenience big tarball and in the binary releases. If you still need it, 
there's still the source version of the last release, which works perfectly.

There is no broken backwards compatibility promise and there are no reasons 
yet to go for Qt 6.
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

More information about the Development mailing list