[Releasing] Removal of engin.io from Qt 5.7

[Jędrzej Nowacki]

What is the idea for Qt5.6 which is LTS? Does it make sense to include 
QtEnginio there?

Cheers,
  Jędrek

On Tuesday 26 of January 2016 07:45:12 Knoll Lars wrote:
> +1 for removing. It doesn’t make a whole lot of sense to have it without the
> backend :)
 
> Cheers,
> Lars
> 
> 
> 
> 
> On 26/01/16 08:30, "Releasing on behalf of Turunen Tuukka"
> <releasing-bounces at qt-project.org on behalf of
> tuukka.turunen at theqtcompany.com> wrote:
 
> 
> > 
> >
> >Hi,
> >
> > 
> >
> >I would like to propose removal of the engin.io cloud service support
> >module Enginio (http://doc.qt.io/qt-5/enginio-index.html) from Qt 5.7
> >release packages. It has
>
> > been deprecated since Qt 5.6 and no longer developed further. 
> > 
> >
> >Also the backend will be shut down most likely during H2/16:
> >
> >http://blog.qt.io/blog/2016/01/26/notification-for-all-qt-cloud-services-us
> >ers
> ><http://blog.qt.io/blog/2016/01/26/notification-for-all-qt-cloud-services-> >users/>
>
> > 
> >
> >There are many good things in the engin.io service, but it never really
> >gained enough momentum. The code of Enginio module remains in the Qt
> >repositories, in case it is later seen useful for further use.
>
> > 
> >
> >Qt is actively used with many different cloud services already. Perhaps
> >with somewhat more effort than was needed to use engin.io. “Cloud
> >compatibility” is very relevant for Qt and with the effort saved from
> >developing
>
> > and maintaining Enginio module, we should be able to improve in that area
> > even further.
>
> >
> >
> > 
> >
> >Yours,
> >
> > 
> > 
> >                             Tuukka
> >
> >
> 
> _______________________________________________
> Releasing mailing list
> Releasing at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/releasing