Qt 6.11 status:
- Qt 6.11.1 release content is frozen, packages are created and final testing 
is ongoing
   * The target was to publish the release Tue 12th May, but it seems we need 
some time to finalize testing. 
   *  The plan is to publish the Qt 6.11.1 release Wed 13th May
 
Qt 6.12 status:
_ Dependency update round in 'dev' succeed and building a snapshot is ongoing
- Qt 6.12 platform and module freeze will be in effect at the end of this 
week(15th May)
- Qt 6.12 feature freeze will be in effect Fri 29th May
   * please start adding Qt 6.12 new features etc in what's new in 6.12 page: 
https://doc-snapshots.qt.io/qt6-dev/whatsnew612.html

Next meeting Tue 19th May 2026 16:00 CET
 
br,
Jani Heikkinen
Release Manager

irc log below:
[17:00:15] <jaheikki3> ablasche: akseli:carewolf: frkleint: lars: mapaaso: 
The-Compiler: thiago: vohi[M]: ping
[17:00:33] <carewolf> pong
[17:00:36] <akseli> jaheikki3: pong
[17:01:03] <thiago> jaheikki3: pong
[17:01:23] <liangqi> pong
[17:01:39] <jaheikki3> Time to start qt release team meeting
[17:01:46] <jaheikki3> on agenda today:
[17:01:49] <jaheikki3> Qt 6.11 status
[17:01:53] <jaheikki3> Qt 6.12 status
[17:02:01] <jaheikki3> Any additional item to the agenda?
[17:03:19] <jaheikki3> Let's start from 6.11 status
[17:03:50] <jaheikki3> Qt 6.11.1 release content is frozen, packages are 
created and final testing is ongoing
[17:04:17] <jaheikki3> The target was to publish the release today, but it 
seems we need still some time to finalize testing
[17:04:38] <jaheikki3> So the plan is to publish the release tomorrow
[17:04:58] <jaheikki3> Luckily it seems everything is OK for the release
[17:05:23] <jaheikki3> That's all about 6.11 status at this time. Any comments 
or questions?
[17:06:41] <jaheikki3> Then 6.12 status
[17:07:01] <jaheikki3> Dependency update round in 'dev' finally succeed and 
building a snapshot is ongoing
[17:07:17] <jaheikki3> 6.12 platform and module freeze will be in effect at the 
end of this week(15th May)
[17:07:41] <jaheikki3> Staging in qt5.git#dev will be restricted from Mon 18th 
May ->
[17:07:44] <carewolf> I hope we can still add the rust toolchain that stalled
[17:08:06] <jaheikki3> Restrictions will be in place until 6.12 is branched 
from the dev
[17:08:18] <thiago> rust? For qtwebengine?
[17:08:23] <carewolf> thiago: yes
[17:08:27] <carewolf> and we need it in 6.12
[17:08:34] <thiago> Ah, ok
[17:08:45] <liangqi> I hope 
https://codereview.qt-project.org/c/qt/qtbase/+/733351 will get approved for 
HarmonyOS. cc thiago
[17:08:58] <jaheikki3> carewolf: any ETA?
[17:09:33] <carewolf> the patch for macos is just waiting on module update so 
it can integrate, it had a build error in webengine, which was patched over a 
week ago, but has dependencies been updated?
[17:09:55] <jaheikki3> liangqi: Yes, and it would be good to get ci related 
changes in before freeze as well
[17:10:17] <carewolf> I can update the windows patch for next week. 
[17:10:33] <liangqi> the new round submodule update is ongoing from today, 
https://codereview.qt-project.org/q/topic:%22dependency_round_1bd4b08a25%22
[17:10:44] <jaheikki3> carewolf: dependencies are updated, the succeed round is 
based on ea2f1dd9934f56094dcbc090e35acb4043cd1f36
[17:10:48] <thiago> liangqi: in progress, but I don't see any looming deadlines 
requiring rushing
[17:10:53] <carewolf> okay. then it can integrate nwo
[17:11:13] <carewolf> https://codereview.qt-project.org/c/qt/qt5/+/706327
[17:11:16] <thiago> I'm mostly happy with the Core portions, just pending a few 
updates that I've requested
[17:11:53] <thiago> there are two still in discussion: the IPC code and 
QThread::terminate()
[17:11:53] <liangqi> thiago: addressed all comments from today. and we will 
continue fixing the issues were raised by maintainers.
[17:12:29] <thiago> the latter you'll probably agree; the former, you may not, 
but if you don't I will not oppose. Our IPC code is broken beyond repair, so I 
don't care if you make it even worse.
[17:12:57] <carewolf> of course webengine will also be separate for 6.12, but 
for now we are using the same versions and will release shortly after 6.12, and 
then things will depend on what management decides
[17:13:00] <liangqi> thiago: HarmonyOS is a new platform, we want to be part of 
6.12, thanks.
[17:13:15] <thiago> liangqi: I know, but again I don't see a looming deadline
[17:14:00] <thiago> I don't expect users to want to use in 6.12, though. They 
may wait for another release.
[17:14:50] <liangqi> thiago: May 14 is public holiday in Europe
[17:15:31] <liangqi> thiago: We have customers are waiting for it in 6.12
[17:15:54] <jaheikki3> thiago: liangqi: let's try to get initial base change + 
CI related changes in during this week, before the platform freeze and if that 
doesn't happen let's agree how to proceed in next meeting. The intention of the 
freeze it to stop qt5 and provisioning related changes close to FF to make sure 
CI is as operational as possible
[17:16:25] <thiago> liangqi: I don't think that's a problem. Like I said, I 
think it will make it to 6.12.
[17:16:38] <liangqi> thiago: thanks
[17:16:41] <jaheikki3> Qt 6.12 feature freeze will be in effect Fri 29th May
[17:17:02] <thiago> May 25th is a public holiday in the US, BTW
[17:18:49] <jaheikki3> And just a reminder, please start adding Qt 6.12 new 
features etc in what's new in 6.12 page: 
https://doc-snapshots.qt.io/qt6-dev/whatsnew612.html
[17:19:35] <jaheikki3> It would be good to get the page as good as possible 
already in Beta1, which will be released soon after the feature freeze
[17:19:56] <jaheikki3> That's all at this time. Any more comments or questions?
[17:21:49] <liangqi> thiago: we have reverted those two changes. will continue 
the discussion after the first change got merge, thanks.
[17:22:16] <thiago> thanks
[17:22:22] <jaheikki3> Ok, let's then end this meeting now & have new one Tue 
19th May at this same time.
[17:22:35] <jaheikki3> Thanks for your participation, bye!
[17:22:57] <liangqi> bye
[17:23:07] <thiago> bye


-- 
Development mailing list
[email protected]
https://lists.qt-project.org/listinfo/development

Reply via email to