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, Lars On 14/09/16 09:36, "Development on behalf of Morten Sorvig" <development-bounces+lars.knoll=qt...@qt-project.org on behalf of morten.sor...@qt.io> wrote: >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 2016, at 20:33, Jake Petroules <jake.petrou...@qt.io> wrote: >> >> 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 <thiago.macie...@intel.com> >>> wrote: >>> >>> 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 provide SSL capabilities on iOS. >>> >>> WTH? Why are we removing options in a patch release? What happened? >>> >>> Is the backend so severely broken that it needed to be removed? >>> -- >>> Thiago Macieira - thiago.macieira (AT) intel.com >>> Software Architect - Intel Open Source Technology Center >>> >>> _______________________________________________ >>> Development mailing list >>> Development@qt-project.org >>> http://lists.qt-project.org/mailman/listinfo/development >> >> -- >> Jake Petroules - jake.petrou...@qt.io >> Consulting Services Engineer - The Qt Company >> Qbs build tool evangelist - qbs.io >> >> _______________________________________________ >> Development mailing list >> Development@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/development > >_______________________________________________ >Development mailing list >Development@qt-project.org >http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
