Hi,
Il 08/12/20 23:55, Kevin Kofler via Development ha scritto:
Raising the bar: apart from some cases of API problems in 6.0, would it
be feasible to do a BC break after every LTS? We might find more
annoyances we want to fix.
IMHO, the compatibility breaks at every major (first-digit, e.g., Q
Sorry, hit enter too fast
On Tue, 8 Dec 2020 at 18:31, Lisandro Damián Nicanor Pérez Meyer
wrote:
>
> Hi!
>
> On Tue, 8 Dec 2020 at 17:47, Benjamin TERRIER wrote:
> [snip]
> > Aren't LTS a commercial only thing now?
> > So doing a BC after an LTS isn't much different than doing it after any
> >
Hi!
On Tue, 8 Dec 2020 at 17:47, Benjamin TERRIER wrote:
[snip]
> Aren't LTS a commercial only thing now?
> So doing a BC after an LTS isn't much different than doing it after any other
> version for distro maintainers and the open source world in general.
With my Debian maintainer hat on: oh *
On Tuesday, 8 December 2020 08:32:51 PST Volker Hilsheimer wrote:
> Hm, every third release is an LTS: 5.9, 5.12, 5.15, perhaps 6.2.
>
> So, that’s every 1.5 years if we stick to the current release cadence.
Which means it either can't be every LTS or the cadence would need to change.
If it's ev
On Tue, 8 Dec 2020 at 17:44, Volker Hilsheimer
wrote:
>
>
> > On 8 Dec 2020, at 16:28, Thiago Macieira
> wrote:
> >
> > On Tuesday, 8 December 2020 01:55:12 PST Giuseppe D'Angelo via
> Development
> > wrote:
> >> Raising the bar: apart from some cases of API problems in 6.0, would it
> >> be fea
Awesome work!! 😊
Cheers,
Tor Arne
On 8 Dec 2020, at 17:51, Alexandru Croitor
mailto:alexandru.croi...@qt.io>> wrote:
Hi again,
A short update on the build system switch.
Sine my last email (half a year ago) a number of issues were raised that we had
to tackle in order to consider switching Q
Hi again,
A short update on the build system switch.
Sine my last email (half a year ago) a number of issues were raised that we had
to tackle in order to consider switching Qt's main build system to CMake.
Some of those issues were tracked in the following JIRA issues
https://bugreports.qt.io/
> On 8 Dec 2020, at 16:28, Thiago Macieira wrote:
>
> On Tuesday, 8 December 2020 01:55:12 PST Giuseppe D'Angelo via Development
> wrote:
>> Raising the bar: apart from some cases of API problems in 6.0, would it
>> be feasible to do a BC break after every LTS? We might find more
>> annoyances
On Tuesday, 8 December 2020 01:55:12 PST Giuseppe D'Angelo via Development
wrote:
> Raising the bar: apart from some cases of API problems in 6.0, would it
> be feasible to do a BC break after every LTS? We might find more
> annoyances we want to fix.
So long LTSs don't happen more often than eve
Hi!
El mar., 8 dic. 2020 08:23, Alexandru Croitor
escribió:
> Hi,
>
> Please check the following comment on JIRA
>
> https://bugreports.qt.io/browse/QTBUG-89170?focusedCommentId=541242
>
> And whether the proposed "approach 3" suits you.
>
> It seems to work already for Christophe's packages as
Hi!
El lun., 7 dic. 2020 16:52, Joerg Bornemann
escribió:
> On 10/27/20 5:34 PM, Thiago Macieira wrote:
>
> > Have we fixed it?
>
> The discussion apparently petered out as everytime this came up - or
> maybe I just missed that we now have consensus on how to name things and
> where to put stuff
Hi all!
We have released Qt 6.0.0 today! Please see more information from Qt 6.0.0
release blog post: https://www.qt.io/blog/qt-6.0-released
Big thanks to everyone involved!
br,
Jani Heikkinen
Release Manager
The Qt Company
___
Development mailing lis
Hi,
Please check the following comment on JIRA
https://bugreports.qt.io/browse/QTBUG-89170?focusedCommentId=541242
And whether the proposed "approach 3" suits you.
It seems to work already for Christophe's packages as they commented on the
issue.
The remaining part would be providing the refe
Il 07/12/20 10:24, Volker Hilsheimer ha scritto:
If we decide here to break BC before 6.1 because the available workarounds [1]
are not applicable or not something we want to live with until Qt 7, then we
might just as well go “all in” with such changes (as long as we maintain source
compatibi
14 matches
Mail list logo
