From jani.heikkinen at qt.io Thu Oct 1 11:46:39 2026 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Thu, 1 Oct 2026 09:46:39 +0000 Subject: [Releasing] Meeting minutes from Qt Release Team meeting 29.09.2026 Message-ID: Qt 6.12 status * Qt 6.12.0 release content is frozen, release packages are created and mostly tested * We will release Qt 6.12.0 Wed 30th September 26 * The target is to release Qt 6.12.1 ~mid November 2026 Qt 6.11 status * Qt 6.11.3 release content is frozen, release packages are created and testing is ongoing * We will release Qt 6.11.3 as soon as possible, maybe this Friday or then next Monday * Qt 6.11.3 will be the last release from Qt 6.11 series Next meeting Tue 13th October 2026 16:00 CET Br, Jani irc log below: [17:00:39] akseli:ankokko: carewolf: frkleint: lars: mapaaso: The-Compiler: thiago: vohi[M]: ping [17:00:51] jaheikki3: pong [17:01:34] jaheikki3: pong [17:01:52] time to start qt release team meeting [17:01:58] On agenda today: [17:02:04] Qt 6.12 status [17:02:07] Qt 6.11 status [17:02:15] Any additional item to the agenda? [17:04:07] Let's start from Qt 6.12 status [17:04:16] Qt 6.12.0 release content is frozen [17:04:35] release packages are created and tested so we are ready for the release [17:04:58] We will release Qt 6.12.0 Wed 30th September 26, if we get 'go' from our PM board [17:05:09] there is some CRA evidence related issues still waiting for their approval [17:05:29] And the target is to release Qt 6.12.1 ~mid November 2026 [17:05:54] That's all about 6.12 status at this time. Any comments or questions? [17:07:55] how does the CRA approval work? [17:10:20] thiago: we have created CRA evidence package based on our processes, ways of working and release readyness status (no open blockers etc). Qt PM Board will have a meeting tomorrow morning to check the package and if all is well enough they approve the evidence and give the 'go' decision [17:11:59] of course this isn't yet official CRA approval, because that kind of process ins't available yet. But this is Qt company internal CRA Ready statement [17:13:12] any more comments or questions? [17:13:48] no, thnaks [17:13:57] Then Qt 6.11 status [17:14:19] Qt 6.11.3 release content is frozen, release packages are created and testing is ongoing [17:14:35] We will release Qt 6.11.3 as soon as possible, maybe this Friday or then next Monday [17:14:47] And Qt 6.11.3 will be the last release from Qt 6.11 series [17:15:07] That's all about 6.11 status. Any comments or questions? [17:17:01] not from me [17:18:10] Ok, it was all at this time so let's end this meeting now & have new one Tue 13th October at this same time; I can't join Tue 6th [17:18:42] thanks for your participation, bye! [17:19:43] bye Confidential -------------- next part -------------- An HTML attachment was scrubbed... URL: From jani.heikkinen at qt.io Wed Oct 14 13:46:06 2026 From: jani.heikkinen at qt.io (Jani Heikkinen) Date: Wed, 14 Oct 2026 11:46:06 +0000 Subject: [Releasing] Meeting minutes from Qt Release Team meeting 13.10.2026 Message-ID: Qt 6.12 status * Qt 6.12.0 is released * The target is to release Qt 6.12.1 17th November 2026 Qt 6.11 status * Qt 6.11.3 release preparations are still ongoing * Some new blockers found and fixing is ongoing. * We will release Qt 6.11.3 as soon as possible, current target is Tue 20th October Qt Webengine status * We are planning to release QtWebEngine and QtPdf 6.140.0 next week Next meeting Tue 20th October 2026 16:00 CET Br, Jani Heikkinen Release Manager irc log below: [16:59:25] akseli:ankokko: carewolf: frkleint: lars: mapaaso: The-Compiler: thiago: vohi[M]: ping [16:59:46] ponh [16:59:48] pong [16:59:57] jaheikki3: pong [17:01:00] time to start qt release team meeting [17:01:06] on agenda today: [17:01:12] Qt 6.12 status [17:01:15] jaheikki3: pong [17:01:15] Qt 6.11 status [17:01:25] Any additional item to the agenda? [17:02:18] jaheikki3: pong [17:02:38] Let's start from Qt 6.12 status [17:03:09] Qt 6.12.0 is released, thanks to everyone once again! [17:03:28] ? [17:03:42] It seems to be quite good release, at least I haven't heard anything alarming so far [17:03:58] The target is to release Qt 6.12.1 17th November 2026 [17:04:30] And release preparations are already started, the first snapshot is built and testing started [17:04:58] That's all about 6.12 status at this time. Any comments or questions? [17:06:08] Ok, then Qt 6.11 status [17:06:23] Qt 6.11.3 release preparations are still ongoing [17:06:52] Some new blockers found and fixing mostly done, fixes for one are still in review [17:07:07] We will release Qt 6.11.3 as soon as possible, current target is Tue 20th October [17:07:23] And as said earlier, 6.11.3 will be the last release from Qt 6.11 series [17:07:37] I thought we'd already closed it all [17:08:24] thiago: I thought the same, but we got new security issues which has to be fixed before release [17:09:11] Any other comments or questions? [17:10:40] Well, we are planning to release QtWebEngine and QtPdf 6.140.0 next week [17:11:01] but it will be first time some unsure of all the steps and who does what [17:11:17] carewolf: yes, true [17:11:58] let's check more about that tomorrow [17:12:04] okay [17:12:34] what webengine version is in 6.12.0? We are actually considering a PySide 6.12.0.1 due to some issues, we might include the new one.. [17:12:42] it was not in 6.12.0 [17:12:50] what? [17:12:57] it is no longer part of Qt [17:13:11] separate release schedule [17:13:36] Well, yes, we bundle it in PySide (extra wheel), but that already was 140.0 for 6.12.0 AFAIK [17:13:45] ah ok [17:14:05] frkleint: it was rc, which were released with the 6.12.0 [17:14:22] Oopsi. I guess I don't want to know.. [17:14:26] or at the same time with 6.12.0 [17:14:28] right 6.140.0-rc was parallel with 6.12.0 [17:14:56] Hm, ok. then it looks we bundled that with PySide 6.12.0 [17:15:53] It was all at this time so let's end this meeting now & have new one Tue 20th October at this same time [17:16:03] Thanks for your participation, bye! [17:16:05] see you [17:16:22] bye [17:16:27] bye Confidential -------------- next part -------------- An HTML attachment was scrubbed... URL: