It’s happening! - Quassel 0.13.0
Hi all, 1312 days have gone by since the last feature release of Quassel IRC. At times, the project went almost dormant; then it was buzzing with activity a...
Hi all, 1312 days have gone by since the last feature release of Quassel IRC. At times, the project went almost dormant; then it was buzzing with activity a...
Hi all, It’s that time of the year again for another Quassel release! For 0.11.0, we’ve focused mainly on full support for Qt 5.2+ (in addition to Qt 4.6+, ...
Hi all, the last update in the 0.9.x series has been released only a few weeks ago, and now it’s already time for another one. Besides various bugfixes (amo...
TL;DR: If you’re running Quassel Core or the stand-alone, monolithic client with Qt 4.8.5+ and PostgreSQL, you need to upgrade immediately! Looks like Qt ch...
Yes, yes, I know. Again I have been too quiet on this page, while several major changes have happened in my real life. However, things are slowly settling do...
Has been a while that this page has seen updates, as we, the main developers, are still too busy with real life to get as much done as we would like. So many...
On September 8th, the IRC was in turmoil because someone discovered and actively exploited a bug in Quassel’s CTCP handling that would cause the core to cras...
Because people keep wondering why our repository has been rather… quiet for the past few months, and not everybody finds his way into our IRC channel to ask ...
It’s that time of the year when we’re releasing a new Quassel, and this time we strongly recommend updating your core or monolithic client at least, as in ol...
In a few days, the master branch (which will become quassel-0.7) will start depending on Qt 4.6 for the client only. Besides giving us some very welcome API ...
Following KDE’s example, Quassel’s master branch (what will become 0.7.x) will require CMake >= 2.6.4 for building starting in May (about two weeks from n...