Qt 6.9 status * Qt 6.9 API change review done & final changes to the declarative are integrating * Qt 6.9 Beta3 content is still not frozen yet, there is still a problem with dependency update in qtdeclarative * The target is to release Qt 6.9.0 Beta3 as soon as possible, let's see if that can still happen during this week or not * We will branch '6.9.0' from ' 6.9' immediately after beta3 content is frozen * The target was to release Qt 6.9.0 RC at the end of February but because of delays with beta3 we might need to delay it a bit * Release blocker list here: https://bugreports.qt.io/issues/?filter=27122
Next meeting Tue 25th of February 2025 16:00 CET br, Jani Heikkinen Release Manager irc log below: [17:00:23] <jaheikki3> ablasche: akseli: carewolf: frkleint: lars_: mapaaso: The-Compiler: thiago: vohi[M]: ping [17:00:26] <thiago> jaheikki3: pong [17:00:34] <akseli> jaheikki3: pong [17:00:35] <vohi[M]> jaheikki3: pong [17:01:24] <jaheikki3> Time to start qt release team meeting [17:01:30] <jaheikki3> on agenda today: [17:01:33] <jaheikki3> Qt 6.9 status [17:01:41] <jaheikki3> Any additional item to the agenda? [17:03:04] <jaheikki3> Ok, let's browse through the 6.9 status [17:03:38] <jaheikki3> Qt 6.9 API change review done & final changes to qtdeclarative is integrating [17:04:24] <jaheikki3> Qt 6.9 Beta3 content is still not frozen yet but the target is to create beta3 packages from next successful dependency update round [17:04:47] <jaheikki3> Dependency update in qtdeclarative finally succeed in 'dev', try ongoing in 6.9 with the fixes [17:05:06] <jaheikki3> And the target is to release Qt 6.9.0 Beta3 as soon as possible, let's see if that can still happen during this week or not [17:05:20] <jaheikki3> We will branch '6.9.0' from ' 6.9' immediately after beta3 content is frozen [17:05:40] <jaheikki3> The target was to release Qt 6.9.0 RC at the end of February but because of delay with beta3 we might need to delay it a bit [17:05:50] <jaheikki3> Release blocker list here: https://bugreports.qt.io/issues/?filter=27122 [17:06:10] <jaheikki3> that's all at this time. Any comments or questions? [17:07:04] <thiago> I've removed my blocker [17:07:11] <thiago> why is QStringRef a blocker? [17:08:31] <jaheikki3> thiago: most probably it isn't meant to be a blocker but the bot has added 6.9.0 as fix version [17:08:36] <thiago> ok, that's a side-effect of some changes having integrated, but the task still being open [17:08:39] <thiago> it's not a blocker [17:08:41] <thiago> yeah [17:08:58] <jaheikki3> I have already asked a confirmation about that from marc [17:09:04] <thiago> I don't think we should be touching Qt5Compat at all, but that's not my call [17:09:12] <vohi[M]> Would only be a blocker if there APIs that used to take a QStringRef, now take a QAnyStringView, and cannot be called anymore with existing code. But we shouldn't change APIs in Qt5Compat, and that's the only place where we use QStringRef... [17:09:15] <vohi[M]> agree [17:09:42] <thiago> it wouldn't be a blocker anyway because those APIs have not used QStringRef since 6.0 [17:09:48] <jaheikki3> Ok, based on that I will remove it from the list. thanks! [17:10:00] <thiago> this may be a regression, but several years old [17:10:12] <jaheikki3> yeah [17:10:25] <thiago> on the QtQuick DLL linking error, I suggest we simply force-disable LTCG for that module. [17:10:37] <thiago> I've posted the comment there. The workaround is simple. [17:11:21] <jaheikki3> thiago: Thanks [17:12:15] <jaheikki3> it was all at this time so let's end this meeting now & have new one Tue 25th February at this same time. [17:12:26] <jaheikki3> thanks for your participation, bye! [17:13:18] <thiago> bye [17:15:54] <vohi[M]> bye! [17:17:32] <frkleint> bye
-- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development