-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to QT6 #16340
Comments
Thanks for the issue. We've had on our radar for a while to upgrade to QT6, but it's quite a big undertaking. That is why we haven't started out yet. |
Can you provide a roadmap for the transition to Qt6? This will allow us to break down the process into small, manageable steps and gradually implement the changes. Here is a preliminary roadmap that we can discuss and refine:
What do you think about this roadmap? Are you ready to start work on the first stage - assessing the current state? Do I understand correctly that currently, both Qt5 and Qt6 are needed to build the application? I'll be happy to assist with any of these stages. |
Correction here. Standard 5.15 is "End of support" Latest commercially available Qt 5.15 is 5.15.17 (May 22, 2024): Source code available for Qt 5.15.15 (Aug 31, 2024 - 1 year gap): This doesn't mean I'm against the upgrade to Qt6 though. |
@Fhiss currently only Qt 5 is needed to build the app. Thank you for the roadmap, it looks really good. The biggest problem with transition to |
Problem:
Status Desktop, being a key component of the Status ecosystem, still uses the outdated QT5 version, which limits its capabilities for future updates and improvements. The End of Support for Qt 5.15 LTS was on 2023-05-26. Let's consider the possibility of transitioning to QT6.
Reasons for transitioning to QT6:
Transitioning to QT6 will be an important step in the development of Status Desktop. This change will benefit both users and developers of Status.
The text was updated successfully, but these errors were encountered: