[Releasing] Meeting minutes from Qt Release Team meeting 25.03.2025
Jani Heikkinen
jani.heikkinen at qt.io
Wed Mar 26 06:29:18 CET 2025
Qt 6.8 status
* Qt 6.8.3 release content is frozen, packages are created & testing is mostly done
* We will release Qt 6.8.3 later this week
Qt 6.9 status
* Qt 6.9.0 release blocker list is empty and Qt 6.9.0 release content was frozen. Unfortunately one new blocker found & fix needs to be taken in
* The target is still to release Qt 6.9.0 Mon 31st March
Next meeting Tue 15th of April 2025 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:07] <jaheikki3_> alblasch: akseli: carewolf: frkleint: lars__: mapaaso: The-Compiler_: thiago: vohi[M]: ping
[17:00:44] <vohi[M]> jaheikki3_: pong
[17:00:55] <carewolf> pong
[17:01:19] <thiago> jaheikki3_: pong
[17:02:13] <jaheikki3_> Time to start qt release team meeting
[17:02:18] <jaheikki3_> on agenda today:
[17:02:20] <jaheikki3_> Qt 6.8 status
[17:02:24] <jaheikki3_> Qt 6.9 status
[17:02:35] <jaheikki3_> Any additional item to the agenda?
[17:03:53] <jaheikki3_> Let's start from Qt 6.8 status
[17:04:21] <jaheikki3_> Qt 6.8.3 release content is frozen, packages are created & testing is mostly done
[17:04:52] <jaheikki3_> The target release Qt 6.8.3 later this week, maybe already tomorrow
[17:05:17] <jaheikki3_> It depends on how quickly we are able to get remaining items done
[17:05:38] <jaheikki3_> that's all about QT 6.8.3 status. Any comments or questions?
[17:07:38] <jaheikki3_> Ok, then Qt 6.9.0 status
[17:07:52] <jaheikki3_> Qt 6.9.0 release blocker list is empty and Qt 6.9.0 release content is frozen
[17:08:03] <jaheikki3_> Release package creation is ongoing
[17:08:06] <thiago> sorry, I found one yesterday
[17:08:18] <jaheikki3_> thiago: ID?
[17:08:22] <thiago> the qthread changes ended up with a no-op
[17:08:51] <thiago> https://codereview.qt-project.org/c/qt/qtbase/+/634258
[17:09:25] <thiago> the task itself was reported as a memory leak, but a) the leak can't be fixed in the library and b) it was a symptom that led me to find the real issue
[17:11:10] <jaheikki3_> and this is really must have for Qt 6.9.0? Because re-creating packages at this point causes a risk for the release schedule...
[17:11:24] <jaheikki3_> vohi[M]: any opinion?
[17:11:29] <thiago> I would prefer
[17:11:42] <thiago> because we're leaking the main thread QAdoptedThread, so we'll get a bunch of bug reports about that
[17:11:54] <thiago> more importantly, the fix may introduce issues and I'd rather people see them in .0 than in 6.9.1
[17:12:39] <vohi[M]> yeah, would be nice to get this in; autotests should catch if this breaks something, I think
[17:12:51] <vohi[M]> thiago: move the change to 6.9.0 and pick it to dev
[17:13:34] <jaheikki3_> yeah, that way we can speed up the progress.
[17:14:18] <thiago> I can do that
[17:14:20] <thiago> moving all three changes
[17:15:28] <jaheikki3_> Ok, so let's take that still in. Hoping CI behaves and we can get packages for testing tomorrow
[17:15:51] <jaheikki3_> vohi[M]: please review changes and I'll stage those in after approval
[17:16:24] <jaheikki3_> but after that release content is frozen and target is to release Qt 6.9.0 Mon 31st March
[17:16:40] <jaheikki3_> that's all about QT 6.9 status at this time
[17:16:47] <jaheikki3_> Any comments or questions?
[17:19:42] <jaheikki3_> it was all at this time so let's end this meeting now. If we managed to release Qt 6.9.0 as planned we can skip next week's meeting. And I am on vacation week after that so let's have next meeting Tue 15th April at this same time
[17:19:57] <thiago> Happy Easter if I don't talk to you
[17:20:08] <jaheikki3_> Same to you all!
[17:20:30] <jaheikki3_> thanks for your participation, bye!
[17:20:39] <vohi[M]> Thanks, Happy Easter and see you in Munich, I hope! :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/releasing/attachments/20250326/343af896/attachment-0001.htm>
More information about the Releasing
mailing list