[Development] Where and how does Qt define which platforms are supported?

Thiago Macieira thiago.macieira at intel.com
Wed Oct 30 15:16:54 CET 2013


On quarta-feira, 30 de outubro de 2013 09:47:49, Turunen Tuukka wrote:
> >>On sexta-feira, 25 de outubro de 2013 07:49:47, Koehne Kai wrote:
> >>
> >>> I think we should have only:
> >>> + Reference Platforms
> >>> + Supported Platforms
> >>> + Platforms Reportedly Working

> This type of three tier approach is good for me as well, perhaps finding
> another term than 'Supported' for the mid tier. The current system of 3 +
> 1 tiers is a bit too complex and partially misleading especially between
> Reference and Tier 1.
> 
> Thiago, Lars and all others interested to join, should we sit down next
> week during the DevDays and develop this further? For example Wednesday?
> 
> For reference, the commercial side has three categories defining how
> support team provides responds and how the platforms are expected to work:
> 
> -> Primary (ones actively verified and known to work, including Qt Project
> Reference and Tier 1 platfroms according to the current definitions and
> some more)
> -> Secondary (ones known to work and tested, typically the Tier 2 of Qt
> Project platforms and some more)
> -> Platforms not covered by standard support (i.e. supported only in case
> the customer has special agreement, including ancient Qt versions and
> exotic configurations)
> 
> The term 'supported' is a bit loaded, so it would be good to have the Qt
> Project Tiers named with descriptive names that use other words.

Sounds like we only need to refine the names that Kai proposed, but we all 
agree we should have three categories only.

I only arrive at 21:05 in SFO on Wednesday. We can do it over a late dinner 
there, but I expect that by this time people will already be having beer in 
the hotel bar.
-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20131030/86f3de25/attachment.sig>


More information about the Development mailing list