So a couple days ago, I had a nice surprise in my mailbox:
Sent by jussi01 all the way from Finland to Germany, as a huge Thank You for the development team :) Needless to say that, while it might not increase productivity at our next devmeeting, it surely increases the dev team's motivation to continue to make Quassel rock!
Thanks a bunch jussi01, and we're looking forward to crack that bottle open for reaching the Ballmer Peak soonish :)
On an unrelated note, the Quassel team will be present at the Qt Developer Days in Munich next week, so if you happen to attend those, be sure to have a chat with us :)
After quite a long while, we finally present to you a new shiny Quassel IRC release! It so happened that we decided to call it 0.3.0.1, which, as attentive readers will certainly notice in an instant, is not the long-expected 0.2.0 (and not even 0.3.0, for that matter). So, uhm, what's up with those Quassel developers and their versioning scheme?
As some of you know, we have been working on a rewrite of the old ChatWidget for quite some time now, and it was always planned that this rewrite would end up as a 0.3 release, whereas the old ChatWidget would live in 0.2. It turned out that we would not only rewrite the ChatWidget (which is now called ChatView), but also most of the client-side message handling. We have switched to a Model-View-Controller-based architecture now. Other than being much easier to maintain and improve on, this approach also allows maximum resource sharing (for example, a chatline is now only stored once, no matter how many ChatViews display it). This results in a Quassel Client that needs much less RAM than versions from the 0.2 branch. Also, we have been (and still are) working on making things more efficient both time- and space-wise, and the current 0.3.0.1 client is already much leaner and meaner than 0.2.0-rc1.
In addition to that architectural rewrite and the optimizations, with the new ChatView and its new and improved code base we could finally start adding new features and improvements to your chat window. So you'll notice a bunch of new stuff, like visible column handles, a last-seen remember line, in-buffer search and more. I won't give you a comprehensive list of new features this time, since it's just too much - just check it out for yourself!
Just to give you a heads-up: With the release of 0.2.0 (which we expect during the next few weeks) we'll switch to a versioning scheme that is more consistent to other projects. This means that from then on, we will be releasing new patch-level releases rather than going the alpha/beta/rc cycle. The latter made sense as long as we didn't have a version that we considered complete enough to be a real release. Based on user feedback and our own experience, we feel quite confident about releasing 0.2.0 very soon now.
After being on a bugfixing spree the past couple of weeks, the Quassel Team proudly gives you our first-ever Release Candidate of what shall become quassel-0.2.0. Since the 0.2 branch has been in feature freeze for a while, you probably won't find much new stuff (except for the occasional feature that might have crept in completely unnoticed of course ;-)), but on the other hand you will also find less bugs than in the previous releases, so grab it while it's still steaming!
After our switch to Git as our version control system, we now also have changed our build system from qmake to CMake. Long-time Quassulans will know that we already had a CMake-based build system before switching to qmake in the first place :) Back then, we decided we'd need qmake to support Qtopia, plus CMake was quite clumsy at the time (and our old build system was uber-complex). Now, it has turned out that we can easily generate Qtopia build files from any build system, plus in the meantime our qmake stuff has grown much more complex than the old system ever was - and it came to the point where qmake just couldn't do all we needed it to do anymore.
As of now, we have switched our public repository from Subversion to Git. While Git takes some time getting used to, it makes development easier for us, and also it is hip and shiny and new - plus what's good for Linus can't be bad for us, eh? :)
You can access the public repo as follows:
git clone git://git.quassel-irc.org/quassel.git
Yep, Your's Truly will be present at Linuxtag in Berlin this Wednesday till Saturday! As I did at CeBIT in March, I'll be helping out at the Amarok booth again. If you happen to be at Linuxtag as well, don't hesitate to stop by at the booth and say hello!
Yes, we can finally announce the release of Quassel's very first beta! With entering the beta cycle, we also enter feature freeze for the 0.2 branch. While we are still stabilizing this branch, we are busy working on tons of new features and larger arch changes in the 0.3 branch, which we'll probably talk about in another blog entry soon...
Read on for the release notes for quassel-0.2.0-beta1!
Got asked today what's happening on the Quassel front, since there haven't been many commits in the past few days, which, after several weeks of frantically committing stuff, is quite unusual... To calm down everybody: even though all devs currently are quite busy at work and in the so-called, yet mythical "Real Life" (which explains while we have gotten somewhat more quiet lately), we are still working on Quassel as well :) Read on for details on Quassel's current state and our plans for the near future!