Qt 6.6 status:

  *   Qt 6.6.1 released
  *   Target is to release Qt 6.6.2 by the end of January 2024

Qt 6.7 status:

  *   Platform and module freeze -milestone in effect
  *   Qt 6.7 Feature Freeze will be in effect Fri 8th of December
  *   Branching from 'dev' to '6.7' will happen Monday 11th of December
  *   Target is to release Qt 6.7 Beta1 immediately after dependency update 
succeed in '6.7'

Next meeting Tue 12th of December 16:00 CET

br,
Jani Heikkinen
Release Manager

irc log below:
[17:00:28] <+jaheikki3> ablasche: : akseli: carewolf: frkleint: mapaaso: 
The-Compiler: thiago: vohi: ping
[17:00:40] <vohi> jaheikki3: pong
[17:01:13] <frkleint> jaheikki3: pong
[17:01:45] <carewolf> pong
[17:02:22] <+jaheikki3> Time to start qt release team meeting
[17:02:26] <+jaheikki3> on agenda today:
[17:02:29] <+jaheikki3> Qt 6.6 status
[17:02:32] <+jaheikki3> Qt 6.7 status
[17:02:42] <+jaheikki3> Any additional item to the agenda?
[17:04:29] <+jaheikki3> Let's start from Qt 6.6 status
[17:05:10] <+jaheikki3> Qt 6.6.1 was released 27th November
[17:05:25] <+jaheikki3> So far it seems to be quite good release
[17:05:45] <+jaheikki3> The target is to release Qt 6.6.2 by the end of January 
2024
[17:06:14] <+jaheikki3> That's actually all about Qt 6.6 status at this time. 
Any comments or questions?
[17:07:50] <+jaheikki3> Ok, then Qt 6.7 status
[17:08:10] <+jaheikki3> Platform and module freeze -milestone is in effect
[17:08:29] <thiago> jaheikki3: pong
[17:08:57] <+jaheikki3> Adding new prebuild binaries (llvm mingw & Linuc on 
arm) in the repositories ongoing
[17:09:15] <+jaheikki3> Qt 6.7 Feature Freeze will be in effect Fri 8th of 
December
[17:09:29] <+jaheikki3> Branching from 'dev' to '6.7' will happen Monday 11th 
of December
[17:09:49] <+jaheikki3> And the target is to release Qt 6.7 Beta1 immediately 
after dependency update succeed in 'dev'
[17:09:57] <+jaheikki3> Sorry, in '6.7'
[17:10:27] <+jaheikki3> That's all about 6.7 status. Any comments or questions?
[17:10:31] -*- thiago has two unifnished features
[17:10:39] <thiago> one was the int128 suppotr that I had promised marc but 
forgot to work on
[17:10:50] <+jaheikki3> thiago: Hoping you can get those ready early enough
[17:10:52] <thiago> the other was the QMetaMethod::listInvoke I promised Thomas 
Zander and also didn't work on
[17:11:26] <thiago> listInvoke is finishable, only unit tests are missing
[17:12:56] <+jaheikki3> what about the int128 support? thiago: vohi: if those 
won't be ready by the FF are those critical enough to get an exception
[17:12:59] <vohi> some of int128 support (as per 
https://bugreports.qt.io/browse/QTBUG-116924) seems to be done and/or in 
progress
[17:13:33] <vohi> if all that's not done yet is missing qHash support, then 
that's ok to make an exception for IMHO
[17:13:37] <thiago> no work has been done since 6.6 release when I argued we 
shouldn't jump the FF
[17:13:41] <thiago> but we didn't develop the feature
[17:13:59] <thiago> we're missing proper printing of them (QDebug, QTextStream)
[17:14:03] <thiago> QLocale
[17:15:51] <vohi> we will either way not be worse off with 6.7 than we are with 
6.6; we can decide for individual items and patches if we want them to be in 
6.7, if they are not merged by time of branching
[17:17:48] <+jaheikki3> yeah, let's check those later if needed. But hoping 
most of important items will be in at FF; the time from FF to final release is 
a bit shorter than earlier...
[17:18:22] <+jaheikki3> This was all about 6.7 status at this time. Is there 
more comments or questions?
[17:20:18] <+jaheikki3> It seems it was all at this time so let's end this 
meeting now & have next one Tue 12th December as planned
[17:20:30] <+jaheikki3> Thanks for your participation, bye!
[17:20:46] <vohi> thanks!
[17:20:55] <carewolf> bye
[17:22:24] <frkleint> bye
_______________________________________________
Releasing mailing list
Releasing@qt-project.org
https://lists.qt-project.org/listinfo/releasing

Reply via email to