[Releasing] Removal of engin.io from Qt 5.7

[Pau Garcia i Quiles]

Hello,

Has releasing the backend as open source been considered?

On Tue, Jan 26, 2016 at 8:45 AM, Knoll Lars <Lars.Knoll at theqtcompany.com>
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-users
> <
> 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
>



-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20160126/0924796f/attachment.html>