Qt 6.8 status
* Qt 6.8.3 is released. It will be the last public release from Qt 6.8 LTS
* Public '6.8' branch will be closed Tue 22nd of April, see
https://lists.qt-project.org/pipermail/development/2025-April/046296.html
Qt 6.9 status
* Qt 6.9.0 released, the target is to release Qt 6.9.1 ~mid May 2025
* Branching from '6.9' to '6.9.1' will start at the beginning of May
Qt 6.10 status
* Plan is to update snapshot after next successful dependency update round
in 'dev'
* Qt 6.10 platform and Module freeze will be in effect 16th of May
* It is time to start adding new modules etc in CI and packages
* Qt 6.10 feature freeze will be in effect at the end of May
Next meeting Tue 29th of April 2025 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:10] <+jaheikki3> ablasche: akseli: carewolf: frkleint: lars_: mapaaso:
The-Compiler: thiago: vohi[M]:
[17:00:23] <vohi[M]> jaheikki3: pong
[17:00:38] <thiago> jaheikki3: pong
[17:01:32] <+jaheikki3> time to start qt release team meeting
[17:01:38] <+jaheikki3> on agenda today:
[17:01:43] <+jaheikki3> Qt 6.8 status
[17:01:47] <+jaheikki3> Qt 6.9 status
[17:01:51] <+jaheikki3> Qt 6.10 status
[17:02:00] <+jaheikki3> Any additional item to the agenda?
[17:03:33] <+jaheikki3> Let's start from Qt 6.8 status:
[17:03:48] <+jaheikki3> Qt 6.8.3 is released and it will be the last public
release from Qt 6.8 LTS
[17:04:05] <+jaheikki3> Public '6.8' branch will be closed Tue 22nd of April,
see https://lists.qt-project.org/pipermail/development/2025-April/046296.html
[17:04:24] <+jaheikki3> that's all about Qt 6.8 status. Any comments or
questions?
[17:05:57] <+jaheikki3> Then Qt 6.9 status:
[17:06:28] <+jaheikki3> Qt 6.9.0 is released and the target is to release Qt
6.9.1 ~mid May 2025
[17:06:47] <+jaheikki3> It means branching from '6.9' to '6.9.1' will start at
the beginning of May
[17:06:56] <thiago> tumbleweed has already updated to 6.9
[17:06:59] <thiago> clearlinux too
[17:07:09] <thiago> there were quite a few source-incompat (missing headers)
problems
[17:07:47] <thiago> and two relating to QString::arg() char16_t, which was an
intentional change
[17:08:01] <vohi[M]> missing headers as in, side-effects of us not including
unnecessary stuff anymore in our public headers?
[17:08:02] <thiago> fortunately, one of them revealed a bug in the application
code itself
[17:08:06] <thiago> yeah
[17:08:52] <thiago>
https://invent.kde.org/plasma/breeze/-/commit/9df8a685aa2d7ed1e9e633dda96d141c591f398e
and
https://invent.kde.org/plasma/plasma-vault/-/commit/a982e58679caa583ceb4cc883d1c1923dab54db9
are missing-include fixes for example
[17:09:14] <thiago>
https://github.com/musescore/MuseScore/commit/05056ed19520060c3912a09a3adfa0927057f956
is the bug fix
[17:11:41] <vohi[M]> thanks; not unexpected that transitive includes are
unreliable between framework versions, although perhaps we might be a bit too
eager with cleaning things up.
[17:12:26] <thiago> missing includes happen and not just to us
[17:12:41] <thiago> I don't think we should fear that
[17:13:07] <thiago> the QString-char change was an intentional source break.
What we should do is find the issues and submit fixes downstream early.
[17:13:54] <+jaheikki3> thanks!
[17:14:10] <thiago> peppe asked that we build some OSS software in
QTQAINFRA-7104
[17:14:19] <thiago> probably something for us to discuss at QtCS in a few weeks
[17:14:40] <thiago> (hmm... "OSS Software" is an example of "RAS Syndrome...")
[17:16:27] <vohi[M]> KDE is now building their code against snapshots (or at
least betas) of Qt in their CI (as advisory), that might be a more scalable
approach. But yeah, good discussion for Qt CS (and otherwise the JIRA ticket)
[17:16:48] <+jaheikki3> I'll discuss with Jukka about QTQAINFRA-7104 as well
[17:18:14] <+jaheikki3> I think this was all about 6.9 at this time so next Qt
6.10 status
[17:19:01] <+jaheikki3> The target is to update public snapshot in the
installer after next successful dependency update round in 'dev'
[17:19:47] <+jaheikki3> And just a reminder: Qt 6.10 platform and Module freeze
will be in effect 16th of May and feature freeze at the end of May
[17:20:09] <+jaheikki3> So it is time to start adding new modules etc in the CI
and packages
[17:20:49] <+jaheikki3> that's actually all about 6.10 status at this time. Any
comments or questions?
[17:22:23] <+jaheikki3> Let's then end this meeting now & have new one Tue 29th
of April at this same time; I can't join Tue 22nd
[17:22:33] <+jaheikki3> thanks for your participation, bye!
[17:23:38] <vohi[M]> bye!
[17:25:35] <thiago> vbye
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
