This is the first release and I would be very happy if more users gave me their feedback. I intend to move to git.kde.org soon in order to leverage the KDE infrastructure (mostly translations, bug tracker, releases)… This also means: There are no translations yet! I also intend to update my OBS repository to provide packages for the first release.

I’m happy to announce the immediate availability of KDevelop 4.1 RC 1. This is a testing release, and any feedback is greatly appreciated. Please send us your feedback either via one of our mailing lists, #kdevelop on freenode or put general bugs and wish request as always to http://bugs.kde.org. We are quite confident that this release is ready for every-day use, and if nothing unplanned happens, we are going to release KDevelop 4.1 in about two weeks.

I have a problem that I could not solve nor find help by my usual paths. I’m speaking about a deadlock on shutdown I get sometimes with what will become KDevelop 4.1. You can find a backtrace in this bug report:

The thing is this: Apparently some global QMutex is getting destroyed by the exit handler but the call to __pthread_cond_destroy does not return.

I have no clue on how to fix this. Is there at least a way to find out which mutex this is? Someone told me to have a look in /proc/PID/maps but there I only found out that - what a suprise - ~QMutex is defined in libQtCore.so… Or should I have looked for the this=0xfffffe00 address? Speaking of which - isn’t that address messed up?

I’m happy to announce the immediate availability of KDevelop 4.1 Beta 3. This is a testing release, any feedback is greatly appreciated. But keep in mind that it might exhibit unexpected behavior and eat your children. Please send us your feedback either via one of our mailing lists, #kdevelop on freenode or put general bugs and wish request as always to http://bugs.kde.org.

I was on a spontaneous trip last week and missed the Beta 2 release. Apol took over but my instructions where not clear enough and the packages where totally screwed up (the tags pointed to code in master, no the 4.1 branch).

I’m in the process of fixing things up and will create tarballs for Beta 3 and announce it to packagers later today.

Lets hope the actual release for users out there can happen later this week.

Yeah, I couldn’t sleep well after I put colors on Dr Konqi. I also did the same for Kate, if you did not notice it. There is a new GDB Backtrace syntax highlighting file for it, giving you the same pleasant experience you are now used to from Dr Konqi. Awesome.

But well, lets admit it: What use are these two for bug triaging? Visit any crash report on bko and you are left to plain old black-on-white… Stone-age stuff, lets put it on LSD, shall we not? I propose: The GDB Backtrace highlighter GreaseMonkey userscript!

please don’t use KDevelop master with KDELibs 4.5.1 or lower. Katepart in that version misses a crucial commit that makes KDevelop crash. It is fixed for 4.5.2. In the meantime you have on of the following options:

This is a bugfix only release and everyone is urged to upgrade as soon as
possible. Users should wait for their distributions to provide packages for
them. The tarballs contain changelogs if you are interested what happened
since 4.0.1. Or read them online:

This is a preview release. We are gratefully welcoming any testers and
feedback to polish it further for the final 4.1 release which will probably
happen around mid October. Please put the reports on the usual places, e.g.
http://bugs.kde.org. If you are interested in the (quite long) list of
changes, look into the tarballs again for an extensive git changelog. If you
just want a few highlights: Git Support Plugin, External Script Plugin,
general polishing, CPP support improvements, lots of bug fixes, UI polishing,
performance improvements, … you name it :)

For the fun of it, here the list of commits changes for 4.1 (imo far too big to show anything useful):

before I go on a short one-week vacation, I wanted to leave you a short note about the outcome of my GSOC, where I tried to revive the Quanta+ brand.

First up, I passed, many thanks to my mentor Andras Mantia. But well, it’s not like I got that for free. In a first estimation I did about 500 commits to Quanta, PHP and KDevplatform in the last three months. So I hope you all agree that I deserve the Google money :)

But lets talk about what I planned to achieve and what I actually achieved:

the XML/HTML plugin is working quite well but is still requiring lots of polishing

the browser preview plugin is supposedly being worked on by another studen in Brazil, I’m awaiting her first results and will polish it together with her.

you still cannot rename tags and automatically rename the close tag as well or similar

the multilang branches have imo nice API additions and seem to work reasonably well. At least my test cases of CSS inside HTML worked fine for me

Anyhow, on one hand I’m personally satisfied with what I achieved code wise, esp. looking at the diffs and knowing how many iterations some of the multilang structures required. On the other hand I had hoped to achieve much more. A first alpha release of Quanta is really not visible to me in the near future.

But, and here I make a promise I do intend to keep: I won’t desert Quanta. Quite the contrary. KDevelop will probably keep my main focus, but I do intend to improve Quanta, esp. merge the multilang branches into KDevplatform for example. My intended time plan contains a note to merge multilang after the movingrange branches into KDevplatform 1.2. Lets see how that works out.

The XML plugin I will definetly continue to polish and make it work as good as possible. Even now it is helpful for more than just web developers: I personally already rely on it when working on Kate language files for example. So there is a personal desire to have it working as good as possible, even though I don’t do much/any web development these days.

Bla bla bla, enough rambling and dumping my thoughts. Lets close this up by saying: Have a nice week, cya soon, hopefully well rested and ready to kick some more code lines :)