> -Original Message-
> From: Arno Rehn
> Sent: Wednesday, July 12, 2023 4:13 PM
> To: EXT Mitch Curtis ; Qt development mailing list
>
> Subject: Re: [Development] Behavior-changing bugfixes in patch-level releases
>
> Hi Mitch,
>
> On 12.07.2023
Hey,
> We do generate release notes for patch release, i.e.
> https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.5.1/release-note.md
> where this particular change is included in the “Important Changes”
> section:
>
> On 12 Jul 2023, at 09:52, EXT Mitch Curtis via Development
> wrote:
>
> Hi Arno,
>>
>> Hey everyone,
>>
>> what is the policy for adding behavior-changing bugfixes to patch-level
>> releases? Is this something to expect?
>> At the moment we operate under the assumption that bumping the
Hi Mitch,
On 12.07.2023 09:52, EXT Mitch Curtis wrote:
Context: We have been hit by
https://codereview.qt-project.org/c/qt/qtdeclarative/+/472596
(which is even marked as "Important Behavior Change") ending up
only in 6.5.1. It was quite the headache figuring out that 6.5.0 ->
6.5.1 has broken
Hi Arno,
> -Original Message-
> From: Development On Behalf Of
> Arno Rehn
> Sent: Wednesday, July 12, 2023 3:01 PM
> To: Qt development mailing list
> Subject: [Development] Behavior-changing bugfixes in patch-level releases
>
> Hey everyone,
>
>
Hey everyone,
what is the policy for adding behavior-changing bugfixes to patch-level
releases? Is this something to expect?
At the moment we operate under the assumption that bumping the
patch-level of Qt is pretty much a no-brainer and can be done without
having to do much in the way of
