Re: [Development] Changing Qt's Binary Compatibility policy

2024-06-18 Thread Thiago Macieira
On Tuesday 18 June 2024 07:53:32 GMT-7 Giuseppe D'Angelo via Development wrote: > I think this is now effectively a separate thread of discussion, since > these deprecations create source incompatibilities, not binary > incompatibilities. > > Should we discuss it at the QtCS in a couple of slots?

Re: [Development] Changing Qt's Binary Compatibility policy

2024-06-18 Thread Giuseppe D'Angelo via Development
Hi, On 18/06/2024 10:15, Alex Blasche via Development wrote: Our biggest issue is the adoption of Qt by users moving from one major release to the next. The deprecations start to become a liability and while they keep SC compatibility in check for Qt 6 they become a serious concern for any ado

Re: [Development] Changing Qt's Binary Compatibility policy

2024-06-18 Thread Alex Blasche via Development
>From: Development on behalf of apoenitz > >Sent: Friday, 14 June 2024 19:32 >There are by now ~240 QT_DEPRECATED_VERSION_X_6_* in qtbase alone. Fixing them >today involves touching thousands line of code in my code base(s). Very few of >them are truly, c

Re: [Development] Changing Qt's Binary Compatibility policy

2024-06-14 Thread apoenitz
On Mon, May 27, 2024 at 09:55:37AM +0200, Giuseppe D'Angelo wrote: > Hi, > > On 25/05/2024 13:03, apoenitz wrote: > > As an open source application developer I mostly care about SC, as SC > > breakages > > means actual work for/me/. > > To better understand: when you talk about SC, are you refer

Re: [Development] Changing Qt's Binary Compatibility policy

2024-05-31 Thread Allan Sandfeld Jensen
On Thursday 30 May 2024 15:56:26 CEST Volker Hilsheimer via Development wrote: > My larger concern is that for patch releases, we have no processes to avoid > that we end up adding poor APIs. We don’t do a header review, and we don’t > have a whatsnew documentation file. The changelog should be eno

Re: [Development] Changing Qt's Binary Compatibility policy

2024-05-30 Thread Volker Hilsheimer via Development
> On 29 May 2024, at 05:30, Kevin Kofler via Development > wrote: > > Giuseppe D'Angelo via Development wrote: >> 2) We stop guaranteeing forward binary compatibility within the same >> minor version. >> >> In other words, code compiled against Qt X.Y.Z may or may not work if at >> runtime Qt X

Re: [Development] Changing Qt's Binary Compatibility policy

2024-05-29 Thread Thiago Macieira
On Wednesday 29 May 2024 16:54:33 GMT-3 Narolewski Jakub wrote: > Sorry for chiming in uninvited but isn't this how the Qt Online Installer > thingy works? Very carefully. It's built on a reasonably old Linux distribution, the oldest of all of them that are still supported. It also builds with a

Re: [Development] Changing Qt's Binary Compatibility policy

2024-05-29 Thread Narolewski Jakub
Sorry for chiming in uninvited but isn't this how the Qt Online Installer thingy works? I know that with it I can install some prebuilt Qt distribution on my Linux - openSUSE Tumbleweed - and I kinda always assumed that the actual build host could be a different distro. I never really gave it much

Re: [Development] Changing Qt's Binary Compatibility policy

2024-05-29 Thread Thiago Macieira
On Wednesday 29 May 2024 00:30:12 GMT-3 Kevin Kofler via Development wrote: > There is, however, one use case you are overlooking, and that is binaries > compiled on one distribution and run on another. That's not supported at all and that has nothing to do with Qt. Unless the two distributions a

Re: [Development] Changing Qt's Binary Compatibility policy

2024-05-28 Thread Kevin Kofler via Development
Giuseppe D'Angelo via Development wrote: > 2) We stop guaranteeing forward binary compatibility within the same > minor version. > > In other words, code compiled against Qt X.Y.Z may or may not work if at > runtime Qt X.Y.W is used, with W > Details: no user downgrades Qt and therefore has eve

Re: [Development] Changing Qt's Binary Compatibility policy

2024-05-27 Thread Giuseppe D'Angelo via Development
Hi, On 25/05/2024 13:03, apoenitz wrote: As an open source application developer I mostly care about SC, as SC breakages means actual work for/me/. To better understand: when you talk about SC, are you referring to literally source compatibility (application can be recompiled with newer vers

Re: [Development] Changing Qt's Binary Compatibility policy

2024-05-26 Thread apoenitz
On Fri, May 24, 2024 at 06:29:41PM +0200, Giuseppe D'Angelo via Development wrote: > Hi, > > One of the discussions at the past Qt Contributors' Summit was about our BC > policy: > > https://wiki.qt.io/Two-way_BC_in_Patch_Releases > > We had a consensus for implementing some changes, but I don'

Re: [Development] Changing Qt's Binary Compatibility policy

2024-05-24 Thread Thiago Macieira
On Friday 24 May 2024 13:29:41 GMT-3 Giuseppe D'Angelo via Development wrote: > Details: no user downgrades Qt and therefore has ever needed this. This > is something that only Qt developers themselves have possibly needed -- > seems to be a historical remnant at this point. > > Concretely, this m

[Development] Changing Qt's Binary Compatibility policy

2024-05-24 Thread Giuseppe D'Angelo via Development
Hi, One of the discussions at the past Qt Contributors' Summit was about our BC policy: https://wiki.qt.io/Two-way_BC_in_Patch_Releases We had a consensus for implementing some changes, but I don't remember the action points have been taken, so here we are. We propose to change Qt's BC po