Qt 4.3.5: Two steps back and one step forward

Published Wednesday May 28th, 2008
7 Comments on Qt 4.3.5: Two steps back and one step forward
Posted in KDE, News, Qt

Earlier this month, we released the single, largest release of Qt since the 4.0.0 release two years ago. Qt 4.4.0 is the result of 10 months of hard work by the Trolls, including numerous distractions. And while it’s being digested by our clients and users, we’re working on Qt 4.4.1, which will include fixes for bugs that were already known at the time of the 4.4.0 release, as well as some that people have reported.

In the meantime, we take two steps back, to the 4.3.x series, and then one step forward: we’re releasing today Qt version 4.3.5. This release is meant for those who cannot upgrade to Qt 4.4.0 yet, but need fixes for some important issues. All of the changes done for 4.3.5 will be present in 4.4.1 and some are even part of 4.4.0 already.

This is the first time ever we’re doing a public release of the previous minor series. In the past, we’ve always stopped development of the previous minor series when the next one came out. Sure, we’ve done security fixes when needed and Trolltech Support continued to support clients using them, but we’ve never made a public release. So this is news for us too. ๐Ÿ™‚

One of the main reasons that made us decide to release 4.3.5 was the sheer size of the 4.4.0 upgrade. Many customers are scared to take the leap. Not that 4.4.0 is a bad release — no, far from it, all indications so far are that it is a great release. (At least, the Trolltech head of Support hasn’t tried to kill me yet for it!) But nonetheless, we decided we would reassert our commitment to all clients and users despite all distractions, by providing them with one more 4.3 release.

If this proves to be a good thing, we may repeat it for the 4.4.x branch when Qt 4.5.0 is released, although we’re not expecting anything as groundbreaking for that release as 4.4.0 was. We also have two or three bugfixes up our sleeves in the 4.3 branch, which may lead to a 4.3.6 release if necessary.

Including the pictures of the Qt developer team again, since a few more people have been patched in.

Oslo team Berlin team
Oslo team Berlin team
Do you like this? Share it
Share on LinkedInGoogle+Share on FacebookTweet about this on Twitter

Posted in KDE, News, Qt

7 comments

Uwe Thiem says:

Wow! Is the fix for that pesky SSL bug part of 4.3.5?

Uwe

Jason says:

Well, I can think of one awesome feature for the trolls to add.

One of the areas I could really use help in is web services. Qt is ideally suited for enabling legacy code to become a web service, and to connect QObjects to web services for transparent web-service usage. Microsoft is pushing web service developers to .Net, but this leaves a large proven code base behind in a forced a rewrite. Qt, being C++ and “just a library” can enable that code base without introducing a large Q/A process. Only the Qt-binding code would have to be tested.

There are two new tools Qt needs:
WSDL to QObject class generator (feed a WSDL file, get a corresponding class with public slots (It would be better if this could be done at run-time, via QMetaObject, but I don’t see a run-time addMethod())
QObject to WSDL generator (feed a QObject file, get a WSDL file exporting public slots) (It would be better if this could be done at run-time …)

Finally, provide an easy way to hide the HTTP communication.

Thiago Macieira says:

Uwe: we have fixed a lot of issues in Qt, both in 4.3.5, 4.4.0 and recently for 4.4.1. That means I have no idea of which particular bug you’re referring to… The Task Tracker should provide the information you want, as well as the 4.3.5 changelog.

Jason: blogs are not the place for feature suggestions. Use the Task Tracker please.

Jeff says:

Jason,

I think what Thiago meant to write was,

“Jason: Thank you for your suggestion. It’s actually a very good idea and could I ask you to please post it (and future suggestions) in the Task Tracker so that it (they) can be formally recognised. Thanks again for the input.”

See, isn’t life better when we all play nice?

coh says:

@uwe: I believe you mean the bug within the (debian-)OpenSSL library regarding bad random numbers. In that case, the answer is of course not, because Qt is linking to the platform’s OpenSSL library and shipping it (iirc). Also, the debian security advisory says clearly that the bug is limited to debian (and linux distributions based upon it, f.e. ubuntu).

coh says:

and not shipping it [together with Qt]. sorry for the typo.

mxttie says:

“since a few more people have been _patched_ in.”
gotta love the wording of that phrase =)

Commenting closed.

Get started today with Qt Download now