Qt 6.6 status:
* Qt 6.6.3 preparations started
* Branching from '6.6' to '6.6.3' done
* The target is to release Qt 6.6.3 Fri 22rd March 2024
Qt 6.7 status:
* Qt 6.7.0 RC content frozen and packages available in the production
* Release announcements will be sent later today, after production tests
are finalized.
* The target is to release Qt 6.7.0 Tue 26th March 2024
* Release blocker list here:
https://bugreports.qt.io/issues/?filter=25675
Next meeting Tue 19th March 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:01:06] <+jaheikki3> ablasche: akseli: carewolf: frkleint: mapaaso:
The-Compiler: thiago: vohi: ping
[17:01:29] <thiago> jaheikki3: pong
[17:01:31] <akseli> jaheikki3: pong
[17:02:02] <frkleint> jaheikki3: pong
[17:02:40] <+jaheikki3> Time to start qt release team meeting
[17:02:48] <+jaheikki3> On agenda today:
[17:02:51] <+jaheikki3> Qt 6.6 status
[17:03:00] <+jaheikki3> Qt 6.7 status
[17:03:12] <+jaheikki3> Any additional item to the agenda?
[17:04:19] <+jaheikki3> Let's start from Qt 6.6 status
[17:04:42] <+jaheikki3> Qt 6.6.3 preparations started
[17:05:10] <+jaheikki3> Branching from '6.6' to '6.6.3' is done and first
dependency update round in '6.6.3' succeed
[17:05:36] <+jaheikki3> Plan is to create first snapshot for RTA later this week
[17:05:46] <+jaheikki3> And the target is to release Qt 6.6.3 Fri 22rd March
2024
[17:06:11] <+jaheikki3> And like said earlier it will be the last release from
the Qt 6.6 series
[17:06:33] <+jaheikki3> That's all about Qt 6.6 status at this time. Any
comments or questions?
[17:08:07] <+jaheikki3> Ok, then Qt 6.7 status:
[17:08:40] <+jaheikki3> Qt 6.7.0 RC content frozen, packages created and
release available in the production
[17:09:12] <+jaheikki3> Release announcements will be sent later today (or
tomorrow morning), after production tests are fully done
[17:09:41] <+jaheikki3> The target is to release Qt 6.7.0 Tue 26th March 2024,
2 weeks after the RC (as planned)
[17:10:41] <+jaheikki3> Blocker list for final release here:
https://bugreports.qt.io/issues/?filter=25675
[17:11:00] <+jaheikki3> That's all about 6.7 status at this time. Any comments
or questions?
[17:11:14] <thiago> rc1 is definitely not acceptable
[17:11:24] <thiago> the fix for QProcess has gone in the last 12 hours
[17:11:46] <thiago> it's still going through 6.7 right now
[17:11:52] <thiago> cp to 6.7.0 still pending
[17:13:02] <+jaheikki3> thiago: that's true. We had a discussion about that
with vohi & tuukka and we agreed that we won't block rc anymore because of that
[17:13:55] <thiago> the other fix for QProcess (staged for dev now) fixes
QProcess::startDetached
[17:14:04] <thiago> it's a silent corruption otherwise
[17:14:08] <thiago> P1 level at least
[17:14:15] <+jaheikki3> We can publish RC2 between RC and final if needed but
we really needed to proceed with the RC to be able to get it out for testing &
be able to get final out before Easter
[17:15:56] <+jaheikki3> thiago: what are the changes you are referring? I might
mix those to those API review related ones...
[17:16:21] <thiago> https://codereview.qt-project.org/c/qt/qtbase/+/546770 and
https://codereview.qt-project.org/c/qt/qtbase/+/546895
[17:18:04] <+jaheikki3> Ok, we can take those in between RC and final release.
I'll make sure those will be staged in 6.7.0 immediately when landed there
[17:19:04] <+jaheikki3> Is there some other comments or questions related to Qt
6.7.0 still?
[17:21:27] <+jaheikki3> Ok, then it was all at this time so let's end this
meeting now & have new one Tue 19th March at this same time
[17:21:41] <+jaheikki3> Thanks for your participation, bye!
[17:24:42] <frkleint> bye
_______________________________________________
Releasing mailing list
Releasing@qt-project.org
https://lists.qt-project.org/listinfo/releasing
