[Development] Meeting minutes from Qt Release Team meeting 21.2.2023

[Jani Heikkinen]

Qt 6.5 status

- Qt 6.5 beta3 preparations are ongoing

   * Beta3 content is frozen and packages are created

   * Testing is ongoing

   * Target is to release Qt 6.5.0 beta3 Thu 23rd February

- Soft string freeze is in effect, official string freeze will be announced Mon 27th February 2023



Qt 6.4 status

- Branching is delayed because of issues with dependency update

   * qtquick3d blocked, fixing ongoing

   * Target is to branch '6.4.3' from '6.4' immediately after successfully dependency update round in '6.4'

- Unfortunately this means we can't release Qt 6.4.3 at the end of February as planned

   * Target is to release Qt 6.4.3 beginning of March



Qt 6.6 initial schedule

- Proposal sent to the ML tue 14th February, no objections --> Qt 6.6 initial schedule will be

   * Qt 6.6 Platform and Module freeze 19.5.2023

   * Qt 6.6 Feature Freeze 2.6.2023

   * Qt 6.6 Beta1 14.6.2023

   * Qt 6.6 RC 12.9.2023

   * Qt 6.6 Final release 26.9.2023



Next meeting Tue 28th February 2023 16:00 CET



br,

Jani Heikkinen

Release Manager



irc log below:

[17:00:30] <jaheikki3> akseli: ablasche: carewolf: frkleint_: lars__:mapaaso: The-Compiler: thiago: vladimir-minenko: vohi: ping

[17:01:36] <jaheikki3> time to start qt release team meeting

[17:01:46] <jaheikki3> On agenda today:

[17:01:59] <jaheikki3> Qt 6.5 status

[17:02:02] <jaheikki3> Qt 6.4 status

[17:02:09] <jaheikki3> Qt 6.6 initial schedule

[17:02:17] <jaheikki3> Any additional item to the agenda?

[17:02:22] <thiago> jaheikki3: pong

[17:03:06] <jaheikki3> Let's start from Qt 6.5 status

[17:03:19] <jaheikki3> Qt 6.5 beta3 preparations still ongoing

[17:03:35] <jaheikki3> Beta3 content is finally frozen and packages are created

[17:03:47] <jaheikki3> And testing is ongoing

[17:03:59] <jaheikki3> the target is to release Qt 6.5.0 beta3 Thu 23rd February

[17:04:20] <jaheikki3> Soft string freeze announced this monday

[17:04:35] <jaheikki3> and official string freeze will be in effect Mon 27th February 2023

[17:05:04] <jaheikki3> that's all about Qt 6.5 status at this time. Any comments or questions?

[17:06:21] <jaheikki3> Ok, then Qt 6.4 status

[17:06:31] <jaheikki3> Branching delayed because of issues with dependency update

[17:06:55] <jaheikki3> qtquick3d is blocking the round, fixing is ongoing

[17:07:17] <jaheikki3> the target is to branch '6.4.3' from '6.4' immediately after successfully dependency update round in '6.4'

[17:07:31] <jaheikki3> Unfortunately this means we can't release Qt 6.4.3 at the end of February as planned

[17:07:54] <jaheikki3> But target is to release QT 6.4.3 as soon as possible, somewhere beginning of march

[17:08:05] <thiago> the 6.5 update is working, though?

[17:08:14] <jaheikki3> Yes, it is working ok

[17:08:49] <jaheikki3> it was all about 6.4 status at this time. Any more commets or questions?

[17:09:59] <jaheikki3> Ok, then Qt 6.6 initial schedule

[17:10:17] <jaheikki3> Proposal sent to the ML tue 14th February, see https://lists.qt-project.org/pipermail/development/2023-February/043635.html

[17:10:45] <jaheikki3> There weren't any objections so Qt 6.6 initial schedule is:

[17:10:56] <jaheikki3> Qt 6.6 Platform and Module freeze 19.5.2023

[17:11:05] <jaheikki3> Qt 6.6 Feature Freeze 2.6.2023

[17:11:13] <jaheikki3> Qt 6.6 Beta1 14.6.2023

[17:11:20] <jaheikki3> Qt 6.6 RC 12.9.2023Qt 6.6

[17:11:41] <jaheikki3> Qt 6.6 Final release 26.9.2023

[17:12:08] <jaheikki3> I'll add these dates in qt6.6 releasing wiki asap

[17:12:39] <thiago> sounds good

[17:13:04] <vohi> sounds good, should leave ample buffer before summer holidays start to get a beta out before that

[17:13:20] <jaheikki3> Exactly

[17:13:43] <jaheikki3> It was all at this time so let's end the meeting now and have new one tue 28th February at this same time

[17:13:54] <jaheikki3> Thanks for your participation, bye!

[17:14:02] <vohi> thanks

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20230222/9a46ed4f/attachment-0001.htm>