I am pleased to announce that we released the first beta of Qt 6.1 today. As the first feature update in the Qt 6 series, Qt 6.1 adds some important new functionality and brings support for multiple additional libraries. We will continue to provide subsequent beta releases via the online installer throughout the beta phase.
With Qt 6.0 released in December, we want to provide the first feature update as soon as possible - targeting to release the Qt 6.1.0 end of April. This allows us to bring improvements over the Qt 6.0, provide support for new platforms as well as release some of the additional libraries that were not yet available with Qt 6.0.
For overview of the most important changes in Qt 6.1, please check https://wiki.qt.io/New_Features_in_Qt_6.1
After the first beta released today, we will push out multiple new beta releases using the online installer. With this approach, it is easy for users to test the new features and provide feedback. We are not planning to publish separate blog posts for the subsequent beta releases and release candidate(s). In addition to binaries, source packages of each beta release are also available for those who prefer to build themselves.
I hope many of you will install the Qt 6.1 Beta releases, test and provide feedback to help us to complete Qt 6.1. For any issues you may find, please submit a detailed bug report to bugreports.qt.io. When filing a bug report, remember to mention which beta you found the issue with, check for duplicates and known issues. You are also welcome to join the discussions in the Qt Project mailing lists and developer forums.
Hopefully, people will show the same disdain for you as you've shown to the open-source community and file no bug reports.
@Adrian: Qt 6.1 is available for both open-source and commercial users.
And feature incomplete; it's alpha and for a lot of us unusable. Sticking 5 behind a paywall properly sucks, especially as many of us open source users will be using it for years until Qt 6 reaches feature parity and stability.
I had Qt 5 up and running on an apple DTK within a few hours of it arriving, and I modified the Qt sources to support ARM (barring the web module, which I personally don't use, so it didn't bother me that I couldn't get that to compile).
Now that the macOS ARM port is behind the wall, we're left high and dry.
Qt5 is stable as far as I'm concerned, it does everything I want, but the arm port's hiding has left a sour taste. Maybe you should consider cherry-picking the arm changes back into a branch that is available for open-source users.
I've used Qt for a long time, and I think it's fantastic. I've sung its praises to anybody that would listen. Nothing comes close to it. I get you're a commercial entity, and the LGPL variant is a bit of a problem for you as a commercial software provider, but I wish you should rethink the situation that you and we as open-source users have ended up in.
An olive branch to the OSS users?
I agree, Qt5 was closed too early. It could have been done after Qt6 reached feature parity and stability with Qt5. If you are enterprise and willing to use Qt5.15.x for long time even after Qt6 use is feasable - sure - pay for commercial LTS, live long and prosper. But closing LTS for non-commercial users while Qt6 is still WIP...
I have successfully compiled Qt 5.15.2 for MacOS on an Arm64 Host. Can you please explain what is not working?
It works because some of the changes were public before it got put behind the paywall. I don't know if all modules were working, I know the web engine wasn't the last time I built it. I has Qt up and running on arm the day my DTK arrived and before Qt released patches, so I found out what did and didn't work correctly (the pcre module would crash if using the JIT option).
However, any further fixes, additions, etc to the arm64 build are now behind the paywall, you won't get them if you're not a commercial customer.
Btw. you can still access all the fixes for 5.15.3 from codereview site without any Qt account.
Is this true? There are only a few fixes for QWebEngine. Nothing else. https://codereview.qt-project.org/q/branch:5.15.3
Yeah, see https://codereview.qt-project.org/c/qt/qtbase/+/318024/12/src/plugins/platforms/android/qandroidinputcontext.cpp for example. You just have to search through bugreports.qt.io and see the changes in Gerrit Review.