Re: [Development] NSURLConnection backend in 5.6.2

2016-09-14 Thread Jake Petroules
> On Sep 14, 2016, at 12:46 AM, Lars Knoll wrote: > > That’s the policy we have had all the time. No feature removal or additions, > no API changes in patch level releases. > > If a feature is really unused, or causes larger issues one can of course > discuss exceptions, but it should be a c

Re: [Development] NSURLConnection backend in 5.6.2

2016-09-14 Thread Morten Sorvig
> On 13 Sep 2016, at 20:41, Jake Petroules wrote: > > >> On Sep 13, 2016, at 11:40 AM, Konstantin Tokarev wrote: >> >> >> >> 13.09.2016, 21:33, "Jake Petroules" : >>> Because the APIs are deprecated by Apple so they would have had to be >>> removed/changed soon anyways, especially when an

Re: [Development] NSURLConnection backend in 5.6.2

2016-09-14 Thread Lars Knoll
That’s the policy we have had all the time. No feature removal or additions, no API changes in patch level releases. If a feature is really unused, or causes larger issues one can of course discuss exceptions, but it should be a conscious decision involving the relevant maintainers. Cheers, L

Re: [Development] NSURLConnection backend in 5.6.2

2016-09-14 Thread Morten Sorvig
Should we have a “no feature removal for cleanup reasons in patch releases” policy? That’s easy to understand for everyone and we don’t have to make the "is it obscure enough” judgement. (The build failure could have been easily fixed so I don’t see it as a relevant reason.) Morten > On 13 Sep

Re: [Development] NSURLConnection backend in 5.6.2

2016-09-13 Thread Jake Petroules
> On Sep 13, 2016, at 1:15 PM, Thiago Macieira > wrote: > > On terça-feira, 13 de setembro de 2016 20:01:10 PDT Jake Petroules wrote: >> On Sep 13, 2016, at 12:55 PM, Thiago Macieira >> mailto:thiago.macie...@intel.com>> wrote: > >> On terça-feira, 13 de setembro de 2016 19:44:35 PDT Jake Petr

Re: [Development] NSURLConnection backend in 5.6.2

2016-09-13 Thread Jake Petroules
On Sep 13, 2016, at 1:15 PM, Thiago Macieira mailto:thiago.macie...@intel.com>> wrote: On terça-feira, 13 de setembro de 2016 20:01:10 PDT Jake Petroules wrote: On Sep 13, 2016, at 12:55 PM, Thiago Macieira mailto:thiago.macie...@intel.com>> wrote: On terça-fe

Re: [Development] NSURLConnection backend in 5.6.2

2016-09-13 Thread Thiago Macieira
On terça-feira, 13 de setembro de 2016 20:01:10 PDT Jake Petroules wrote: > On Sep 13, 2016, at 12:55 PM, Thiago Macieira > mailto:thiago.macie...@intel.com>> wrote: > On terça-feira, 13 de setembro de 2016 19:44:35 PDT Jake Petroules wrote: > I'd be blown away if they did and I can't see how the

Re: [Development] NSURLConnection backend in 5.6.2

2016-09-13 Thread Jake Petroules
On Sep 13, 2016, at 12:55 PM, Thiago Macieira mailto:thiago.macie...@intel.com>> wrote: On terça-feira, 13 de setembro de 2016 19:44:35 PDT Jake Petroules wrote: I'd be blown away if they did and I can't see how there would be a dependency. Also using deprecated APIs is a bad idea for app store

Re: [Development] NSURLConnection backend in 5.6.2

2016-09-13 Thread Thiago Macieira
On terça-feira, 13 de setembro de 2016 19:44:35 PDT Jake Petroules wrote: > I'd be blown away if they did and I can't see how there would be a > dependency. Also using deprecated APIs is a bad idea for app store > compliance. I believe there have been rejections for that in the past. But did it wo

Re: [Development] NSURLConnection backend in 5.6.2

2016-09-13 Thread Jake Petroules
On Sep 13, 2016, at 12:32 PM, Thiago Macieira mailto:thiago.macie...@intel.com>> wrote: On terça-feira, 13 de setembro de 2016 18:41:50 PDT Jake Petroules wrote: They can and have before. Anyways, it doesn't matter. The code was unused, untested, and was in the way of other things, so its remova

Re: [Development] NSURLConnection backend in 5.6.2

2016-09-13 Thread Thiago Macieira
On terça-feira, 13 de setembro de 2016 18:41:50 PDT Jake Petroules wrote: > They can and have before. Anyways, it doesn't matter. The code was unused, > untested, and was in the way of other things, so its removal is > inconsequential. > > Also it caused build failure on tvOS/watchOS. Are we sure

Re: [Development] NSURLConnection backend in 5.6.2

2016-09-13 Thread Jake Petroules
On Sep 13, 2016, at 11:40 AM, Konstantin Tokarev mailto:annu...@yandex.ru>> wrote: 13.09.2016, 21:33, "Jake Petroules" mailto:jake.petrou...@qt.io>>: Because the APIs are deprecated by Apple so they would have had to be removed/changed soon anyways, especially when an alternative (which is

Re: [Development] NSURLConnection backend in 5.6.2

2016-09-13 Thread Konstantin Tokarev
13.09.2016, 21:33, "Jake Petroules" : >  Because the APIs are deprecated by Apple so they would have had to be > removed/changed soon anyways, especially when an alternative (which is the > default now) is already available. AFAIK they cannot remove API from released SDK, and users may choose

Re: [Development] NSURLConnection backend in 5.6.2

2016-09-13 Thread Jake Petroules
Because the APIs are deprecated by Apple so they would have had to be removed/changed soon anyways, especially when an alternative (which is the default now) is already available. Also it caused build failure on tvOS/watchOS. On Sep 13, 2016, at 11:25 AM, Thiago Macieira mailto:thiago.macie...@

[Development] NSURLConnection backend in 5.6.2

2016-09-13 Thread Thiago Macieira
The changelog contains this entry: - [QTBUG-45031] The NSURLConnection backend of QNetworkAccessManager has been removed, since SecureTransport is the default SSL backend on iOS and is enabled by default. This means that building with -no-openssl -no-securetransport will no longer provid