Repository navigation
Conversation
|
adding this as release image : https://www.qt.io/hs-fs/hubfs/subscription%20timeline.png?width=1370&name=subscription%20timeline.png |
|
Aha, thanks for that!
So this PR is wrong, it should be the current 2023-05-26 and not 2023-12-08.
So you need a new licence for support up to 2025-05-26. Okay, so we have three EOL dates:
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 could you prepare a new pr just to update releaseimage which shows that photo which i mentioned above ? Thank you |
|
@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 |
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:
And not: