[Development] Can your module be included in Qt 6?

[Lars Knoll]

Hi all,

We’re now closing in on our checkpoint for the structure/platform freeze for Qt 6.0. This means we will start nailing down the final list of modules and platforms that will be part of Qt 6.0 (or released together with 6.0) during next week.

In case you maintain a module in Qt, please have a final look https://wiki.qt.io/Checklist_for_Qt_6.0_inclusion and ensure the data for your module is up to date. If it is not marked as ready there by Monday, it won’t be part of Qt 6.0 and will have to wait for 6.1 before the module can get included.

As you can see, the scope of 6.0 will be reduced compared to 5.15. This is a similar approach to what we did with 5.0, where we also tried to focus on the essential modules first and added other functionality a bit later again.

Cheers,
Lars

On 3 Jun 2020, at 14:55, Alex Blasche <alexander.blasche at qt.io<mailto:alexander.blasche at qt.io>> wrote:

Hi,

I would like to send a gentle reminder to provide the relevant information for the Qt 6 early structure/platform freeze. Several module maintainer have provided the required information (Thank you) but quite a few modules are still missing. There are about 1.5 weeks left for the dead line on the 15. June.

Wiki to be updated: https://wiki.qt.io/Checklist_for_Qt_6.0_inclusion

--
Alex

________________________________________
From: Development <development-bounces at qt-project.org<mailto:development-bounces at qt-project.org>> on behalf of Alex Blasche <alexander.blasche at qt.io<mailto:alexander.blasche at qt.io>>
Sent: Wednesday, 13 May 2020 11:29
To: development at qt-project.org<mailto:development at qt-project.org>
Subject: [Development] Can your module be included in Qt 6?

Hi,

As mentioned earlier on this mailing list [1], Qt 6.0 will have a Structure and Platform Freeze at the end of June. This leaves the open question of what checkpoints are to be met and a dead line.

With the help of several people I took the liberty of drafting  a check list which would make sense at the given time. Please check:

https://wiki.qt.io/Checklist_for_Qt_6.0_inclusion

and provide feedback.

Since we need the freeze by the end of June. I suggest that maintainers provide the raw data via the template mentioned in the above wiki until 15. June. This would leave us 2 weeks to discuss the outcomes and find a consolidated position. I recommend we treat "no reply" as "not ready for 6.0". Otherwise the process may drag out for too long.

Note that several modules have multiple maintainers (e.g. QtGUI). Please engage with your co-maintainers to consolidate the module state.

If you already know today that your module does not hit the 6.0 dead line (and your co-maintainers (if any) agree) please provide the info as soon as possible in the wiki.

--
Alex

[1] https://lists.qt-project.org/pipermail/development/2020-April/039382.html
_______________________________________________
Development mailing list
Development at qt-project.org
https://lists.qt-project.org/listinfo/development
_______________________________________________
Development mailing list
Development at qt-project.org
https://lists.qt-project.org/listinfo/development

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