Skip to content

[Qt] Update 5.15 LTS commercial licence holder EOL - #1091

Closed
hugovk wants to merge 1 commit into
masterfrom
qt-5.15-lts-commerical-eol
Closed

hugovk wants to merge 1 commit into
masterfrom
qt-5.15-lts-commerical-eol

Conversation

@hugovk

@hugovk hugovk commented Apr 22, 2022

Copy link
Copy Markdown
Member

Official support for Qt 5.15 LTS [1]:

"For our open source users, it will be supported in the same way as other regular Qt releases until the release of Qt 6."

-> 2020-12-08 [2]

"For commercial customers, Qt 5.15 will be long-term-supported (LTS) for three years with regular bug fix releases beyond the release of Qt 6. "

-> 2020-12-08 + 3 years = 2023-12-08

[1] https://www.qt.io/blog/qt-5.15-released
[2] https://www.qt.io/blog/qt-6.0-released


There was discussion in #282 about whether to show the commercial licence holder EOL for 5.15, or the earlier open-source one.

Because KDE is releasing the patches as open-source it was decided to show the commercial LTS for open source too.

(This does cause some confusion about EOLs for the Python bindings, PySide2 and PyQt5, but let's not go into that now ;)

So assuming we're sticking with commercial licence holder EOL == open-source EOL, the support info from https://www.qt.io/blog/qt-5.15-released suggests the Qt 5.15 EOL is really:

  • Qt 6 release date + 3 years

And not:

  • Qt 5.15 release date + 3 years

@BiNZGi BiNZGi left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems okay from my side. @usta what do you think?

@BiNZGi
BiNZGi requested a review from usta April 22, 2022 12:32
@usta

usta commented Apr 22, 2022

Copy link
Copy Markdown
Member

@usta

usta commented Apr 22, 2022

Copy link
Copy Markdown
Member

@hugovk

hugovk commented Apr 22, 2022

Copy link
Copy Markdown
Member Author

Aha, thanks for that!

Legacy license holders are operating under standard LTS rules. Thus EoS for Qt 5.15 LTS is 26th May 2023.

So this PR is wrong, it should be the current 2023-05-26 and not 2023-12-08.

If you need technical support for Qt 5.15 beyond 26th May 2023, you can either subscribe to Qt 5.15 Extended Support for your project or convert your legacy licenses to Subscriptions.

So you need a new licence for support up to 2025-05-26.

Okay, so we have three EOL dates:

  • 2020-12-08 for open source users
  • 2023-05-26 for legacy licence holders
  • 2025-05-26 for new licence holders

But we have assumed open source users can still get patches via KDE. Do we assume they can still get patches up until 2025-05-26?

I'll close this PR, and recommend another to update if needed. It should have some descriptive text to help explain these different levels of EOL :)

@hugovk hugovk closed this Apr 22, 2022
@usta

usta commented Apr 22, 2022

Copy link
Copy Markdown
Member

@hugovk could you prepare a new pr just to update releaseimage which shows that photo which i mentioned above ? Thank you
About KDE i dont think they will continue to support it until 2025 but until the end of support of kde plasma 5
we are still on developing the qt6+qt5 ( both ) supported KDE frameworks then kde plasma 6 will be based on it , and looks like it wont will be begining of next year it will be possoble but you know sometimes new devs contribute more and it might be much earlier :)

@usta

usta commented Apr 22, 2022

Copy link
Copy Markdown
Member

@hugovk also if it is ok for you could you add these discustions to talk part of Qt (in endoflife's talk wiki ) so new contributers might follow easily

@hugovk hugovk mentioned this pull request Apr 27, 2022
@hugovk
hugovk deleted the qt-5.15-lts-commerical-eol branch April 27, 2022 13:24
@hugovk

hugovk commented Apr 27, 2022

Copy link
Copy Markdown
Member Author

@marcwrobel marcwrobel added the release-updates Pull Requests that update release information label Aug 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-updates Pull Requests that update release information

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants