Qt 6.4 status: - Qt 6.4.0 release content frozen & release packages created * RTA ongoing - We will release these packages as Qt 6.4.0 Thu 29th September 2022
Confirmed Qt 6.5 schedule: * Qt 6.5 Platform and Module freeze: 25th November 2022 * Qt 6.5 Feature Freeze: 9th December 2022 * Qt 6.5 Beta1: 15th December 2022 * Qt 6.5 RC: 16th March 2023 * Qt 6.5.0 Final release 30th March 2023 Next meeting Tue 11th October 2022 16:00 CET br, Jani Heikkinen Release Manager irc log below: [17:01:07] <+jaheikki3> akseli: ablasche: carewolf_home: frkleint: lars_:mapaaso:The-Compiler:thiago:vohi: ping [17:01:12] <carewolf_home> pong [17:01:17] <thiago> jaheikki3: pong [17:01:25] <vohi> pong [17:01:51] <+jaheikki3> Time to start Qt release team meeting [17:01:55] <+jaheikki3> On agenda today: [17:02:00] <+jaheikki3> Qt 6.4 status [17:02:12] <+jaheikki3> Qt 6.5 schedule [17:02:21] <+jaheikki3> Any additional item to the agenda? [17:04:03] <+jaheikki3> Ok, let's start from Qt 6.4 status [17:04:30] <+jaheikki3> QT 6.4.0 final content was frozen and testing is ongoing [17:05:15] <+jaheikki3> unfortunately @kkoehne just reported https://bugreports.qt.io/browse/QTBUG-107007 and we think we need to fix that one for .0 as well [17:05:53] <+jaheikki3> So we will take this one in & create new packages asap [17:05:56] <carewolf_home> Is it top configuration? Seems like the kind of thing we could update later [17:06:33] <+jaheikki3> well, not sure [17:07:05] <+jaheikki3> But maybe it isn't, it seems we don't have that in our CI or other tests [17:07:21] <vohi> agree, as long as qtbase can be configured with -no-gui this is acceptable, I think [17:07:26] <carewolf_home> well, our CI don't do top-level build but build per module [17:08:33] <carewolf_home> oh, well not a big problem either :shrug: [17:08:56] <thiago> I wouldn't even call -no-gui a showstopper [17:09:14] <vohi> Perhaps enough to have that added to release-test-automation coverage; but I don't think this should stop the show, there are ways to exclude submodules that are very obviously depending on GUI [17:09:58] <+jaheikki3> Ok, lets then keep this as known issue for Qt 6.4.0 and get the fix in 6.4.1 [17:10:29] <+jaheikki3> And of course improve our test to catch this kind of issues earlier [17:10:59] <+jaheikki3> So we will release existing packages as Qt 6.4.0 Thu 29th September as planned [17:11:04] <carewolf_home> not sure we want top-level build steps in integration testing, that takes too long [17:12:16] <+jaheikki3> carewolf_home: yeah, we need to plan to where to add this new test [17:12:45] <vohi> RTA is enough I think, and top-level build testing the source package that we include in the downloads is a good idea anyway, if that's not already done. Not sure that -no-gui is a priority though :) [17:13:41] <+jaheikki3> Yeah, agree. There is something already in RTA but I'll check with johanna if this could be something to be added [17:13:45] <+jaheikki3> But it was all about Qt 6.4 status at this time. Any more comments or questions? [17:13:46] <carewolf_home> I always wanted a lazy tester in the background randomly building with different combinations on and off, and opening bugs when failing something [17:13:55] <carewolf_home> no, questions [17:15:26] <+jaheikki3> Ok, then Qt schedule [17:16:08] <+jaheikki3> In last meeting minutes I proposed the schedule for 6.5, see https://lists.qt-project.org/pipermail/development/2022-September/042983.html [17:16:29] <+jaheikki3> There weren't any objections so the initial schedule for Qt 6.5 will be [17:16:51] <+jaheikki3> * Qt 6.5 Platform and Module freeze: 25th November 2022 [17:16:51] <+jaheikki3> * Qt 6.5 Feature Freeze: 9th December 2022 [17:16:51] <+jaheikki3> * Qt 6.5 Beta1: 15th December 2022 [17:16:51] <+jaheikki3> * Qt 6.5 RC: 16th March 2023 [17:16:51] <+jaheikki3> * Qt 6.5.0 Final release 30th March 2023 [17:18:03] <+jaheikki3> I think it was all at this time. [17:18:42] <+jaheikki3> Let's skip next week's meeting and have new one Tue 11th October at this same time [17:18:57] <frkleint> bye [17:18:59] <+jaheikki3> Thanks for your participation, bye! [17:19:06] <vohi> thanks, bye! _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development