Qt 5.15 LTS Support Extended An Additional Two Years - For Their Paying Subscribers

[phoronix]

Phoronix: Qt 5.15 LTS Support Extended An Additional Two Years - For Their Paying Subscribers

The Qt Company announced they will be maintaining the Qt 5.15 long-term support (LTS) code-base by an additional two years...

https://www.phoronix.com/scan.php?page=news_item&px=Qt-5.15-LTS-Extended-Support

[poncho524]

Is QT6 out of beta yet?

[cl333r]

However, that extra two years of support will continue to be restricted to those that are paying Qt Subscription License customers.

If you're not paying - no soup for you!

[DanL]

Before Alexmitter and others start making a big deal out of this, let me point out that the open source Qt5 patch collection is alive and well:

https://community.kde.org/Qt5PatchCollection

https://invent.kde.org/qt/qt/qtbase/-/commits/dev/

[tildearrow]

<nonsense>The Qt Company loses $4 billion per year from KDE users...</nonsense>

[CommunityMember]

Is QT6 out of beta yet?

Qt 6 has been out of beta for quite some time, and 6.2 (which is considered, more or less, feature complete) was released in Sept. 2021.

Those projects that are not dependent on specific Qt 5 legacy features that have no specific equivalent now just need to resource the migration. Which is easier said than done for (esp.) larger open source projects which have limited ability to resource anything (although KDE is doing it, as they can).

[CommunityMember]

Before Alexmitter and others start making a big deal out of this

There is really no reason to make any deal out of this. Many vendors of commercial products (Microsoft for Windows, RedHat for Enterprise Linux, etc.) offer custom extended long term support contracts beyond the general public EOS dates for their paying customers (typically at quite the premium).

[bug77]

There is really no reason to make any deal out of this. Many vendors of commercial products (Microsoft for Windows, RedHat for Enterprise Linux, etc.) offer custom extended long term support contracts beyond the general public EOS dates for their paying customers (typically at quite the premium).

It's (not so) subtle way of rattling the chains of anti closed source readers

[skeevy420]

That's embarrassing for a multi-million dollar company.

Not a single one of them thought, "Gee, we should right click 'EoS' and add that to our internal dictionary so our chart doesn't make us look like a bunch of doofuses who leave typos all over the place."

On top of that the font in it is aliased. They could have put a bit more effort into that image instead of hitting F11 and cropping it. You'd think a company involved in graphical interfaces would put more effort into their appearance.

You'd think.

[Nth_man]

> There is really no reason to make any deal out of this. Many vendors of commercial
> products (Microsoft for Windows, RedHat for Enterprise Linux, etc.) offer custom
> extended long term support contracts beyond the general public EOS dates for
> their paying customers (typically at quite the premium).

It's (not so) subtle way of rattling the chains of anti closed source readers

It attracts attention, entices users to follow that link and engage in discussions.