Qt 6.6 status
* Branching from '6.6' to '6.6.2' has been delayed. The target is to do the
branching during this week
* The target is still to release Qt 6.6.2 during January
Qt 6.7 status
* Beta2 has been delayed. The target is to release Qt 6.7.0 Beta2 soon
after next successful dependency update round in '6.7'
* Hoping it will happen at the beginning of next week
* API review is proceeding, see https://bugreports.qt.io/browse/QTBUG-119952
* Plan is to create tasks for 3rd party component updated by the end of
this week
Next meeting Tue 23rd January 2024 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[17:00:16] <+jaheikki3> ablasche: Akseli: carewolf: frkleint: mapaaso:
The-Compiler: thiago: vohi: ping
[17:00:24] <vohi> jaheikki3: pong
[17:00:33] <Akseli> jaheikki3: pong
[17:01:34] <frkleint> jaheikki3: pong
[17:02:11] <+jaheikki3> time to start qt release team meeting.
[17:02:17] <+jaheikki3> On agenda today:
[17:02:25] <+jaheikki3> Qt 6.6 status
[17:02:26] <thiago> jaheikki3: pong
[17:02:29] <+jaheikki3> QT 6.7 status
[17:02:43] <+jaheikki3> Any additional item to the agenda?
[17:04:33] <+jaheikki3> Let's browse through the statuses & start from Qt 6.6
one (which is actually pretty much same as it was last time)
[17:05:11] <+jaheikki3> Branching from '6.6' to '6.6.2' delayed because of
issues with dependency updates in '6.6'
[17:05:40] <+jaheikki3> We should have fixes finally in place & already
integrated in 'dev'
[17:05:53] <+jaheikki3> So those should be in '6.6' quite soon as well
[17:06:19] <+jaheikki3> And branching from '6.6' to '6.6.2' will happen after
fixes are in '6.6'
[17:06:34] <+jaheikki3> Hoping that can happen still during this week
[17:06:58] <+jaheikki3> The target is still to release Qt 6.6.2 during January
[17:07:27] <+jaheikki3> I think this is all about Qt 6.6 status at this time.
Any comments or questions?
[17:07:28] <vohi> we have a page of open cherry-picks for 6.6 branches:
https://codereview.qt-project.org/q/status:open+branch:6.6; presumably many
failed for the same reason as the dependency updates.
[17:07:54] <vohi> but also a bunch of unresolved conflicts, so good to get this
cleaned up swiftly
[17:08:00] -*- vohi goes and mashes the stage button
[17:08:53] <+jaheikki3> Yeah, thanks vohi!
[17:09:11] <+jaheikki3> Then Qt 6.7 status:
[17:09:47] <+jaheikki3> Beta2 delayed because of those dependency update issues
[17:10:13] <+jaheikki3> The target is to release Qt 6.7.0 Beta2 as soon as
possible after next successful dependency update round in '6.7'
[17:10:33] -*- thiago thinks the "Fix coffee machine" commit is the most
important in cold weather
[17:10:47] <+jaheikki3> :D
[17:11:38] <+jaheikki3> Dependency update fixes are integrating in '6.7' so
hoping we can get full update round done soon, latest by the end of this week
[17:12:23] <+jaheikki3> And so on beta2 could be released at the beginning of
next week if packages will be good enough for the beta2
[17:12:40] <+jaheikki3> Qt 6.7 API review proceeding, see
https://bugreports.qt.io/browse/QTBUG-119952
[17:13:00] <+jaheikki3> But there is still reviews etc to be done so all help
there is welcome
[17:13:50] <+jaheikki3> Official update round for Qt 6.7 3rd party modules not
started yet but plan is to create tasks for updates by the end of this week
[17:14:30] <+jaheikki3> And it was all about Qt 6.7 status at this time. Any
comments or questions?
[17:16:43] <+jaheikki3> Ok so it was all at this time. Let's end this meeting
now & have new one Tue 23rd January at this same time
[17:16:52] <+jaheikki3> Thanks for your participation, bye!
[17:17:11] <vohi> thanks, bye!
[17:17:22] <carewolf> bye
[17:17:31] <frkleint> bye
[17:17:50] <thiago> bye
_______________________________________________
Releasing mailing list
Releasing@qt-project.org
https://lists.qt-project.org/listinfo/releasing
