Nicolas Fella wrote:
>> The fact that KDE does not use Qt6 yet has rather little to do with
>> the quality of Qt6.
Kevin Kofler (8 September 2022 01:37) replied:
> Where have I claimed that it does? I sense a strawman…
>
> My point is that it takes time for KDE and other downstreams to adopt
> a
El dimecres, 7 de setembre de 2022, a les 14:16:23 (CEST), Tarja Sundqvist va
escriure:
> Hi all,
>
>
>
> we have released Qt 5.15.6 opensource today:
>
>
>
> * release note:
> https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/5.15.6/release-note.
> md * source packages in
On Thursday, 8 September 2022 14:30:36 PDT Albert Astals Cid wrote:
> Oh, sorry for the noise.
No need to apologise. Better to have more a false alarm so we can be sure,
then allow a problem to linger. More eyes on the problem.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud
On Thursday, 8 September 2022 02:23:39 PDT Edward Welbourne wrote:
> The reason we plan for Qt 7 is that it's the next time we can make
> certain kinds of backwards-incompatible changes. When we decide that
> such a change is needed, we plan for it, because we can't do it yet, or
> indeed any
On Thu, 8 Sept 2022 at 18:39, Thiago Macieira wrote:
>
> On Thursday, 8 September 2022 14:30:36 PDT Albert Astals Cid wrote:
> > Oh, sorry for the noise.
>
> No need to apologise. Better to have more a false alarm so we can be sure,
> then allow a problem to linger. More eyes on the problem.
On Thursday, 8 September 2022 14:06:24 PDT Albert Astals Cid wrote:
> Should we restore those symbols or just accept that Qt 6 broke BC a year ago
> and no one realized so why bring the symbols back?
The commit message says
Remove the dead code for blocking methods from QtConcurrent
El dijous, 8 de setembre de 2022, a les 23:23:00 (CEST), Thiago Macieira va
escriure:
> On Thursday, 8 September 2022 14:06:24 PDT Albert Astals Cid wrote:
> > Should we restore those symbols or just accept that Qt 6 broke BC a year
> > ago and no one realized so why bring the symbols back?
>
>
