Qt 6.6 status:
* Qt 6.6.1 release preparations are ongoing
* Branching from '6.6' to '6.6.1' will happen Tue 14th of November
* Target is to release Qt 6.6.1 Thu 23rd of November
Qt 6.7 status:
* Platform and module freeze -milestone will be in effect 24th of November
* No new modules known for Qt 6.7. If there will be any please inform
Jani immediately.
* Possible exceptions can be taken in after FF & Beta1; It is really
important to stop provisioning changes at platform and module freeze.
* Qt 6.7 Feature Freeze will be in effect 8th of December so only a month
time to implement new features for Qt 6.7.
Next meeting Tue 21st of November 16:00 CET
br,
Jani Heikkinen
Release Manager
irc log below:
[16:59:35] <+jaheikki3> ablasche: akseli: carewolf: lars_: mapaaso:
The-Compiler: thiago. vohi: ping
[16:59:44] <vohi> jaheikki3: pong
[17:00:10] <thiago> jaheikki3: pong
[17:00:52] <+jaheikki3> Time to start qt release team meeting
[17:00:58] <+jaheikki3> on agenda today:
[17:01:03] <+jaheikki3> Qt 6.6 status
[17:01:10] <+jaheikki3> Qt 6.7 status
[17:01:18] <+jaheikki3> Any additional item to the agenda?
[17:02:40] <+jaheikki3> Let's start from Qt 6.6 status
[17:02:58] <+jaheikki3> Which is actually pretty much the same as last time:
[17:03:15] <+jaheikki3> Qt 6.6.1 release preparations are ongoing
[17:03:34] <+jaheikki3> Branching from '6.6' to '6.6.1' will happen Fri 10th of
November
[17:04:03] <+jaheikki3> And the target is to release Qt 6.6.1 23rd of November
[17:05:10] <+jaheikki3> That's actually all about qt 6.6 status at this time.
Any comments or questions?
[17:06:01] <vohi> given that it's bug fixing sprint in the company, maybe
branching after that is over makes more sense?
[17:06:26] <vohi> ie. wait for Tuesday 14th
[17:06:46] <+jaheikki3> That's actually true, I'll postpone the branching then
a bit
[17:06:59] <carewolf_home> +1
[17:07:14] <+jaheikki3> So branching will happen Tue 14th
[17:07:25] <+jaheikki3> Thanks for noticing this!
[17:07:53] <+jaheikki3> Ok, then Qt 6.7 status
[17:08:34] <+jaheikki3> Some challenges to get dependency update done in 'dev';
last successful round 20th October
[17:09:10] <+jaheikki3> But known issues should be fixed and new round will be
started when latest fix integrates in qtbase
[17:09:26] <+jaheikki3> Platform and module freeze -milestone will be in effect
24th of November
[17:09:38] <+jaheikki3> No new modules informed so far
[17:10:05] <+jaheikki3> So if there will be any please inform me immediately
[17:10:44] <+jaheikki3> Qt 6.7 Feature Freeze will be in effect 8th of December
so only a month left to implement new features for Qt 6.7
[17:10:56] <thiago> ok
[17:11:12] <+jaheikki3> That's all about Qt 6.7 status at this time. Any
comments or questions?
[17:11:16] -*- thiago needs to finish one feature for QMetaObject::listInvoke
[17:11:20] <thiago> thanks for reminding
[17:11:22] <vohi> we might have some provisioning changes coming in as a
consequence of trying to link dynamically against FFmpeg; are those subject to
the platform/modules deadline?
[17:11:52] <vohi> (in which case I might just as well ask for exception right
away ;))
[17:12:08] <+jaheikki3> vohi: yes, those are. It is really important to stop
provisioning changes at platform/module freeze
[17:13:11] <vohi> agree, those take along time and often have a lot of fallout;
but also important that we stop linking statically against FFmpeg, that library
has a huge attack surface
[17:13:17] <+jaheikki3> vohi: if we need an exception for those that's OK for
me but as usual those exceptions should be taken in only after the FF; after
beta1 is out
[17:14:20] <+jaheikki3> (those platform etc provisioning changes has been
biggest reason for FF/beta1 delays in previous releases and it has been much
easier after we took that milestone in the use)
[17:16:45] <+jaheikki3> It was all at this time so let's end this meeting now.
I can't participate Tue 14th so let's have new meeting Tue 21st at this same
time
[17:17:01] <+jaheikki3> Thanks for your participation, bye!
[17:17:04] <carewolf_home> bye
[17:19:30] <vohi> thanks!
_______________________________________________
Releasing mailing list
Releasing@qt-project.org
https://lists.qt-project.org/listinfo/releasing
