[Development] Minimum Deployment Platforms for 5.7 onwards?

[John Layt]

On 8 January 2016 at 07:18, Turunen Tuukka <tuukka.turunen at theqtcompany.com>
wrote:

>
>
> Hi John,
>
>
>
> This item was discussed at Qt Contributor’s Summit, please see session
> notes: http://wiki.qt.io/QtCS2015_LTS
>
>
>
> For compilers this is also documented to the Qt Base change log:
> http://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.5.1
>
>
>
> For 5.6 the current list of supported platforms and compilers is the
> following: http://wiki.qt.io/Qt-5.6.0-tools-and-versions (note that we
> are working to add OS X 10.11 to CI and fully support it)
>
>
>
> The idea is that by making Qt 5.6 LTS, we gain more freedom to drop older
> (non-c++11) compilers as well as older platforms from Qt 5.7 and subsequent
> versions. Those who have such older platforms to support, are recommended
> to stay with the LTS version for a while. This approach allows us to move
> faster for new features planned for future Qt releases.
>
>
>
> For application developers the documentation is often the best source to
> find the list of supported platforms:
> http://doc.qt.io/QtSupportedPlatforms/index.html This has not yet been
> updated to 5.6, but will be before the final release.
>

Thanks Tuukka, but that's all a bit messy and hard to work out (not to
mention the LTS email threads here which are impossible to follow). It
makes my point really that there's no one canonical source telling us Qt
contributors what platforms we need to design or code features for in the
next Qt release, or for fixes in the last bug release. I need to know what
versions of the platform API's I can use, not what's Official, Reference,
CI, or Community supported.

I've taken the liberty of starting a wiki page to try summarise things the
way I'd like to see them laid out:

https://wiki.qt.io/PlatformSupport

Feel free to edit or fix or move to a more appropriate place.

John.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160108/c9cefc52/attachment.html>