Bug fixes that are only available to commercial license holders... Really?

Diracsbracket · 3 Jul 2021, 12:19

Qt 5.15.3 has over 250 bug fixes:
https://www.qt.io/blog/commercial-lts-qt-5.15.3-released
As a patch release however, it does not add any new functionality.
Yet, the bug fixes are only provided to commercial license holders.
Brilliant!

Qt, please hurry and also cut off access to the various individual patches that
are still accessible from the system dashboard before freeloaders without a
commercial license get to them!

[Moved to The lounge ~kshegunov]

jsulm · wrote on 5 Mar 2021, 06:33

@Diracsbracket Unfortunately, LTS point releases are now commercial only...

sierdzio · wrote on 5 Mar 2021, 06:34

Yeah, dumb move but not unexpected - they announced this way back.

And this is not entirely true:

the bug fixes are only provided to commercial license holders.

because the fixes are provided openly in Qt 6. The catch, of course, is that Qt 6 is practically a proof of concept at this point, with many important modules missing...

JonB · 7 Mar 2021, 10:33

@Diracsbracket

Really?

Yes, Really....

Diracsbracket · 3 Jul 2021, 10:56

@JonB said in Bug fixes that are only available to commercial license holders... Really?:

Yes, Really....

Yeah, I know I am bitching, but it's just that I don't understand the logic behind all this.

It's like to say to their paying customers:
"Look, we found all these bugs in the previous release, and got them fixed in a nice new package, only for you. As for those open-source suckers, they'll have to apply the fixes themselves on this one. That'll show them! Isn't that a bang for your buck?"

Cheers.

kshegunov · wrote on 7 Mar 2021, 12:19

@Diracsbracket said in Bug fixes that are only available to commercial license holders... Really?:

Yeah, I know I am bitching

Eh! When I heard of it, I did too. You are most certainly not uniquely evil in that regard.

but it's just that I don't understand the logic behind all this.

Money. There's a lot of arguments back an forth on the mailing lists. It was rather epic, honestly. If you want to be up to speed on all the drama, the mail list archive is the place to start.

It's like to say to their paying customers:
"Look, we found all these bugs in the previous release, and got them fixed in a nice new package, only for you. As for those open-source suckers, they'll have to apply the fixes themselves on this one. That'll show them! Isn't that a bang for your buck?"

Feels that way, yeah. The official stance for OSS is to upgrade to the next available release, which should include the bugfixes.
My personal opinion: it is a dick move, but then again, life goes on.

Christian Ehrlicher · wrote on 7 Mar 2021, 12:29

I'm pretty sure there will be soon some people who collect all (or at least important) fixes for 5.15.x. Most of them are visible through gerrit so just someone needs to write a script... ;)

DavisTressie · 3 Sept 2021, 05:12

This post is deleted!

Christian Ehrlicher · wrote on 8 Mar 2021, 09:53

You have to follow the respective license(s). But this has nothing to do with this topic.

fcarney · 9 Jun 2021, 10:12

My guess is this will cause a fork in the code base eventually. Someone could in reality make a mirror, point to that mirror with the maintenance tool (--mirror), and use a forked version.

GeorgeLovett · wrote on 15 Mar 2021, 10:19

This post is deleted!

Ayden32 · wrote on 9 Jun 2021, 10:12

This post is deleted!

aditibhatia225 · wrote on 11 Jun 2021, 12:57

This post is deleted!