Cross-platform software libraries and APIs
Qt Creator IDE and productivity tools
UI Design tool for UI composition
Usage intelligence for embedded devices
GUI test automation
Code coverage analysis
Test results management and analysis
Software static code analysis
Software architecture verification
The latest version of Qt.
Make the most of Qt tools, with options for commercial licensing, subscriptions, or open-source.
Explore Qt features, the Framework essentials, modules, tools & add-ons.
The project offers PySide6 - the official Python bindings that enhance Python applications.
Qt empowers productivity across the entire product development lifecycle, from UI design and software development to quality assurance and deployment. Find the solution that best suits your needs.
Insight into the evolution and importance of user-centric trends and strategies.
Learn how to shorten development times, improve user experience, and deploy anywhere.
Tips on efficient development, software architecture, and boosting team happiness.
Get the latest resources, check out upcoming events, and see who’s innovating with Qt.
Whether you're a beginner or a seasoned Qt pro, we have all the help and support you need to succeed.
July 28, 2009 by Carlos Manuel Duclos Vergara | Comments
We all want to get access to new features, but we also want to get stable things. These two goals seems contradictory and in a sense they are. If you want to live in the edge you have to accept some "early adopter problems" but if you want to have only rock solid features, you need to let them mature and "gain experience". With our new open development process people can get access to all of our newly developed features while they are still in the making, therefore gaining valuable insight on what's coming in the next release. The problem appears when people uses that "bleeding edge" code to start developing things, how can we provide "stable bleeding edge" features?
The solution is more or less obvious, have a master branch where everything is committed and a master-stable branch that is slightly behind master but it is guaranteed to compile. It seems simple and problem free, however there is still one pending question. How "slightly behind" is master-stable from master? Up to last week, master-stable was manually updated, which led to fewer updates and not so "bleeding edge" code. From this week on we have implemented automatic update of master-stable, so now master-stable will be updated as soon as everything is ready, no human intervention required.
The system goes like this:
Voila, master-stable updates itself! So from now on you have no excuses not to use master-stable to check out what's happening in Qt while enjoying a "stable bleeding edge" branch.
The avid reader would have noticed that it is the first time my name appears on this blog. I joined Trolltech on September 2007 and I've been the QA manager for Qt for the past two minor releases (4.4 and 4.5) and currently I'm busy handling Qt 4.6 :-)
Download the latest release here: www.qt.io/download.
Qt 6.8 release focuses on technology trends like spatial computing & XR, complex data visualization in 2D & 3D, and ARM-based development for desktop.
Check out all our open positions here and follow us on Instagram to see what it's like to be #QtPeople.
Sep 20, 2024
Qt Gradle Plugin 1.0 (QtGP) build tool has been released. You can include..
Sep 16, 2024
We are happy to announce the release of Qt Tools for Android Studio 3.0...
Aug 30, 2024
Qt/.NET is a proposed toolkit for interoperability between C++ and .NET,..
Qt Group includes The Qt Company Oy and its global subsidiaries and affiliates.