There was already some precedent in the mail chain for it, plus the remaining comments are just about the wording of comments and the missing cherry-pick lines in the commit message – no functional/behavioral changes. Based on what Assam said during a meeting, those comments was all that was left in these, barring any unexpected finds.
From: Ville Voutilainen <ville.voutilai...@gmail.com> Date: Monday, 9. June 2025 at 17.41 To: Petri Virkkunen <petri.virkku...@qt.io> Cc: Jani Heikkinen <jani.heikki...@qt.io>, Qt development mailing list <development@qt-project.org> Subject: Re: [Development] HEADS-UP: Qt 6.10 Feature Freeze On Mon, 9 Jun 2025 at 12:44, Petri Virkkunen via Development <development@qt-project.org> wrote: > > Hi, I’d like to ask for a late exception for two changes extending our Qt > Quick for Android API. > > > > First change: https://codereview.qt-project.org/c/qt/qtdeclarative/+/644210, > reason for the delay is partially due to the tests in the same chain needing > some bugfixing, and that reviews have taken some time to get done, but you > can see from the patch dates that this has not functionally changed since the > patchset uploaded on the 8th of May. It also includes some tests, and is an > extension of the existing functionality, so should be a decently safe bet. > > > > This qtdeclarative change has a supporting patch going into androiddeployqt > here: https://codereview.qt-project.org/c/qt/qtbase/+/644138 which does not > impact API, just extends the Java code gen happening at app build time. On > this change, the last behavioral change (some renaming of generated code) was > on May 21st, and the last major code change was May 8th, so it would’ve made > it into the Feature Freeze if not for waiting for the qtdeclarative change :) I don't understand how it's possible to ask for a freeze-exception for changes that haven't even been +2ed yet.
-- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
