conda-forge / qt-feedstock

A conda-smithy repository for qt.
BSD 3-Clause "New" or "Revised" License
12 stars 57 forks source link

Next LTS release? #200

Closed jaimergp closed 2 years ago

jaimergp commented 3 years ago

Qt 5.12 is EOL on 2021-12-05.

Next LTS is 5.15, but allegedly only for commercial license holders:

With Qt 6.0.0 released and the first patch release (Qt 6.0.1) coming soon, it is time to enter the commercial-only LTS phase for Qt 5.15 LTS. All the existing 5.15 branches remain publicly visible, but they are closed for new commits (and cherry-picks). Exception being the Qt WebEngine (and the deprecated Qt Script), which have a 3rd party LGPL dependency.

Closing happens tomorrow, 5th January 2021. After this the cherry-picks go to another repository that will be available only for the commercial license holders. We will arrange repository access to the commercial license holders, so in addition to the official releases it is possible to use the repositories. Instructions about this will be available to commercial license holders during next week, after we have completed the license change and other preparations.

First commercial-only Qt 5.15.3 LTS patch release is planned to be released in February.

We can arrange access for external module maintainers to the commercial-only repositories. If there is interest, please contact me or Tarja Sundqvist tarja.sundqvist at qt.io who is the release manager for the commercial-only LTS releases.

In practice, I guess that means 5.15 is not LTS for us. So... Qt 6.x it is? The next LTS will be 6.2, but it will have the same treatment as 5.15: once 6.3 is released, LTS will only be available for commercial users.

There's also the KDE-maintained series of patches on top of 5.15.2, which could provide some room there. They don't do releases though.

Thoughts @conda-forge/core?

jakirkham commented 3 years ago

There is PR ( https://github.com/conda-forge/qt-feedstock/pull/198 ), which is trying to add 5.15.2. Though as you say there will not be additional patch releases.

Someone is welcome to try a Qt 6 PR.

A relevant question here is how the whole PyQt, PySide, etc. ecosystem are affected by either change as those are what Python users (seeing xref'd issue link) are most interested in. Idk that answer maybe someone can go study this issue and report back?

jaimergp commented 3 years ago

Oh, I totally missed that PR, thanks for the hint!

I checked for PySide, and only found some tangentially related info about their LTS status in a blog post from 2018:

Note that Qt for Python is tightly bound to a particular Qt version and does not inherit the LTS (three years of support) flag from Qt 5.12. This means that this release is supported for one year starting on its release day. Our aim for the future is to release Qt for Python at the same time as the Qt version that Qt for Python is based on. Unfortunately, our release process has not reached this point quite yet.

Also found this message in their Gitter room, which I guess we were expecting:

User: Hey there :wave:, What is the plan regarding Qt 5.15.3, will there be a 5.15.3 branch? Do you have an estimate when we can expect it? Maintainer: Hey, we are just following what Qt releases. Since 5.15.3 is a commercial only LTS release, there will be no OSS release. The fixes for that version are not critical, nor related to security (at least on Python land), and all of them are included in PySide6. If you are still not on PySide6 due to missing modules, I'm certain that in 6.1 you will have most of the modules you need :)

For PyQt I couldn't find anything worth sharing. Their wheels do vendor parts of Qt itself, so I guess it's expected they they follow what Qt does and stop OSS support at 5.15.2. But Might be wrong.

Tobias-Fischer commented 2 years ago

See https://github.com/conda-forge/qt-feedstock/pull/206