Qt 6.5 status

  *   Branching from '6.5' to '6.5.1' done
  *   Qt 6.5.1 release preparations ongoing
  *   Target is to release Qt 6.5.1 Wed 10th May



Qt 6.6 status

  *   Only a month left to implement new features for Qt 6.6
     *   the whatsnew66.qdoc document here: 
https://code.qt.io/cgit/qt/qtdoc.git/tree/doc/src/whatsnew/whatsnew66.qdoc
        *   Please add new features etc. here as soon as possible
  *   Some challenges to get dependency update done in 'dev'
     *   latest successfully submodule update was 12th April & existing 
snapshot is based on that
  *   API review process improvement started, see 
https://lists.qt-project.org/pipermail/development/2023-May/043803.html



Next meeting Tue 9th May 2023 16:00 CET



br,

Jani Heikkinen

Release Manager



irc log below:

[17:01:21] <+jaheikki3> ablasche: akseli: carewolf_home: frkleint: lars_: 
mapaaso: The-Compiler: thiago: vohi: ping

[17:01:32] <vohi> pong

[17:01:34] <carewolf_home> pong

[17:01:39] <akseli> jaheikki3: pong

[17:01:46] <thiago> jaheikki3: pong

[17:02:14] <+jaheikki3> Time to start qt release team meeting

[17:02:19] <+jaheikki3> On agenda today:

[17:02:22] <frkleint> jaheikki: pong

[17:02:24] <+jaheikki3> Qt 6.5 status

[17:02:40] <+jaheikki3> Qt 6.6 status

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

[17:04:05] <+jaheikki3> Ok, let's start from Qt 6.5 status

[17:04:24] <+jaheikki3> Branching from '6.5' to '6.5.1' done

[17:04:41] <+jaheikki3> Qt 6.5.1 release preparations are ongoing

[17:05:11] <+jaheikki3> All known release blockers should be already fixed

[17:06:03] <thiago> have we re-fixed the moc/qdbusxml2cpp issue?

[17:06:07] <+jaheikki3> Target is to freeze the release content at the end of 
this week &  release Qt 6.5.1 Wed 10th May

[17:06:15] <thiago> the original emergency fix was 6.5.0 only

[17:07:20] <+jaheikki3> thiago: Ahh, that one. Chatted about that with Fabina 
this morning and his plan is to cherry-pick the revert in 6.5.1 as well; the 
fix isn't ready yet

[17:07:37] <+jaheikki3> Fabian I meant to write

[17:07:55] <thiago> https://bugreports.qt.io/browse/QTBUG-110979

[17:09:16] <+jaheikki3> thiago: And this one: 
https://bugreports.qt.io/browse/QTBUG-111330

[17:10:25] <+jaheikki3> vohi: thiago: What do you think, can we live with the 
revert in Qt 6.5.1 or do we need to get the proper fix in? That will most 
likely delay the release but on the other hand we aren't that hurry with it...

[17:10:37] <vohi> the cherry-pick of the revert into 6.5.1 is 
https://codereview.qt-project.org/c/qt/qtbase/+/475342; if we have no better 
fix, then merging that revert is the right course of action

[17:12:42] <+jaheikki3> Yeah, true

[17:14:09] <thiago> we can live with the revert because it's been like that for 
a long time

[17:14:15] <thiago> it's not a regression

[17:14:57] <+jaheikki3> Ok, so let's take the revert in 6.5.1 & try to get the 
issue fixed properly in 6.5.x/6.6

[17:15:48] <+jaheikki3> It was all about Qt 6.5 at this time. Then Qt 6.6 status

[17:16:38] <+jaheikki3> Qt 6.6 feature freeze preparations ongoing

[17:16:57] <+jaheikki3> Only a month left to implement new features for Qt 6.6

[17:17:33] <+jaheikki3> So far only one new module coming in Qt 6.6

[17:17:43] <frkleint> which one?

[17:17:51] <+jaheikki3> qtgraphs

[17:18:07] <frkleint> Oh!!

[17:18:12] <frkleint> fe

[17:18:27] <+jaheikki3> That's not yet in the snapshot but the target is to add 
it asap

[17:18:43] <frkleint> aha, ok, needs PySide bindings..

[17:19:23] <+jaheikki3> We have had light challenges (once again) to get 
submodule updates done in 'dev'

[17:19:41] <+jaheikki3> latest successfully submodule update was 12th April & 
existing snapshot is based on that

[17:20:21] <+jaheikki3> But new round is ongoing & all known issues should be 
fixed so let's hope we can get full update by tomorrow morning

[17:20:55] <+jaheikki3> & so on we could get new snapshot in the installer 
tomorrow

[17:21:23] <+jaheikki3> vohi also started the discussion to improve API  review 
process, see 
https://lists.qt-project.org/pipermail/development/2023-May/043803.html

[17:21:53] <+jaheikki3> So please participate the discussion to get the process 
as smooth as possible

[17:22:18] <+jaheikki3> that's all at this time. Any more comments or questions?

[17:22:24] <vohi> Also: Seems that we had a hiccup with documentation testing 
being disabled after the last CI/Gerrit maintenance, which might need a bit of 
grinding through race conditions where new warnings block the turning-back-on 
of the documentation testing configuration.

[17:22:31] <vohi> And regular reminder to $DEAR_READER that the whatsnew66.qdoc 
document is at 
https://code.qt.io/cgit/qt/qtdoc.git/tree/doc/src/whatsnew/whatsnew66.qdoc :)

[17:23:20] <+jaheikki3> Yeah, thanks

[17:23:51] <+jaheikki3> Let's end this meeting now & have new one tue 9th May 
at this same time.

[17:24:02] <+jaheikki3> Thanks for your participation, bye!

[17:24:18] <vohi> thanks, bye!

[17:24:52] <frkleint> bye
_______________________________________________
Releasing mailing list
Releasing@qt-project.org
https://lists.qt-project.org/listinfo/releasing

Reply via email to