Approved in release team meeting just now. Please cherry-pick the change 
manually, with other required changes that didn’t land in 6.9 yet (seems that 
change alone results in a merge conflict in 6.9).

Volker


> On 9 Dec 2024, at 10:47, Tor Arne Vestbø <tor.arne.ves...@qt.io> wrote:
> 
> The following change, that adds 4 new padding properties to Application 
> Window, did not make through the CI over the weekend: 
> 
> https://codereview.qt-project.org/c/qt/qtdeclarative/+/605277
> 
> I’m officially requesting a feature freeze exception so we can get it in for 
> 6.9
> 
> Cheers,
> Tor Arne
> 
>> On Dec 9, 2024, at 07:21, Jani Heikkinen via Development 
>> <development@qt-project.org> wrote:
>> 
>> Hi!
>> Branching from ‘dev’ to ‘6.9’ is now done and the Qt 6.9 Feature Freeze is 
>> in effect! So from now on all changes targeted to the Qt 6.9 must have 
>> 'Pick-to: 6.9' and 'dev' is for Qt 6.10. If your new feature skipped the 
>> branching, you need either request an exception or wait Qt 6.10.
>>     Staging qt5.git#6.9 will be restricted until Qt 6.9 beta1 is out, but 
>> restrictions in ‘dev’ are removed & you can start staging changes in 
>> qt5.git#dev
>>   br,
>> Jani Heikkinen
>> Release Manager
>>     From: Jani Heikkinen 
>> Sent: perjantai 6. joulukuuta 2024 11.59
>> To: development@qt-project.org
>> Subject: HEADS-UP: Qt 6.9 Feature Freeze
>>   Hi!
>>   Qt 6.9 Feature Freeze will be in effect today. If your changes are ready 
>> and approved by the end of today, you can still continue staging those in 
>> 'dev' over the weekend. The plan is to branch from "dev" to "6.9" on Monday 
>> morning next week.
>>   If your feature isn't ready by the end of today, you'll either need to 
>> postpone it to Qt 6.10 or request an exception.
>>   br,
>> Jani Heikkinen
>> Release Manager
>>   -- 
>> Development mailing list
>> Development@qt-project.org
>> https://lists.qt-project.org/listinfo/development
> 

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Reply via email to