Hi all,
With the feature freeze in place, we should do a systematic review of the APIs
that are new or have undergone larger changes for Qt 6.
The API change review in gerrit that Eddy provided is a good basis, but
probably not enough to discuss some of the larger changes.
To review those, I
On Mittwoch, 26. August 2020 08:46:41 CEST Lars Knoll wrote:
> Hi all,
>
> This is just a gentle reminder that feature freeze for Qt 6 is approaching
> very quickly now. We’ve had a round of checks inside the Qt Company
> regarding how ready the teams are. All in all it looks relatively good, so
>
> On 7 Sep 2020, at 12:10, Edward Welbourne wrote:
>
> Alex Blasche (7 September 2020 09:58)
>> I suggest we exclude reviews for the modules which are not part of Qt
>> 6. It greatly reduces the effort. When a module comes back
>> (e.g. during 6.2) then we have to run a complete 5.15..6.2 revie
Hi all,
Documentation engineers are most often not the right assignee for example bugs,
which end up going stale. I propose to retire the "Examples and demos”
component.
Bugs in examples are often discovered during package testing, or soon after
release of a new minor version. In most cases, d
Alex Blasche (7 September 2020 09:58)
> I suggest we exclude reviews for the modules which are not part of Qt
> 6. It greatly reduces the effort. When a module comes back
> (e.g. during 6.2) then we have to run a complete 5.15..6.2 review
> anyway.
Sounds fair enough. At first sight.
Now I just n
Hi Eddy,
Thank you for getting this started.
I suggest we exclude reviews for the modules which are not part of Qt 6. It
greatly reduces the effort. When a module comes back (e.g. during 6.2) then we
have to run a complete 5.15..6.2 review anyway.
--
Alex
_
