[17:07:52] <jaheikki3_> Qt 6.9.0 release blocker list is empty and Qt 6.9.0 release content is frozen
[17:08:03] <jaheikki3_> Release package creation is ongoing
[17:08:06] <thiago> sorry, I found one yesterday
[17:08:18] <jaheikki3_> thiago: ID?
[17:08:22] <thiago> the qthread changes ended up with a no-op
[17:08:51] <thiago> https://codereview.qt-project.org/c/qt/qtbase/+/634258
[17:09:25] <thiago> the task itself was reported as a memory leak, but a) the leak can't be fixed in the library and b) it was a symptom that led me to find the real issue
[17:11:10] <jaheikki3_> and this is really must have for Qt 6.9.0? Because re-creating packages at this point causes a risk for the release schedule...
[17:11:24] <jaheikki3_> vohi[M]: any opinion?
[17:11:29] <thiago> I would prefer
[17:11:42] <thiago> because we're leaking the main thread QAdoptedThread, so we'll get a bunch of bug reports about that
[17:11:54] <thiago> more importantly, the fix may introduce issues and I'd rather people see them in .0 than in 6.9.1
[17:12:39] <vohi[M]> yeah, would be nice to get this in; autotests should catch if this breaks something, I think
[17:12:51] <vohi[M]> thiago: move the change to 6.9.0 and pick it to dev
[17:13:34] <jaheikki3_> yeah, that way we can speed up the progress.
[17:14:18] <thiago> I can do that
[17:14:20] <thiago> moving all three changes
[17:15:28] <jaheikki3_> Ok, so let's take that still in. Hoping CI behaves and we can get packages for testing tomorrow
[17:15:51] <jaheikki3_> vohi[M]: please review changes and I'll stage those in after approval