blogging live from CeBIT, Hanover, Germant, Worls'd largest IT fair :) This time I am not promoting Quassel, but I am part of the Amarok Promo Team. Be sure to check out the bestest music player in the world! Still using Quassel though :) While part of the KDE and Amarok people here chose to find some restaurant and eat, sven423 and me decided to enjoy the free booth parties :) Since we have only a few more minutes until security kicks us out for good, just a few notes:
A few days later than planned, we have released quassel-0.2.0-alpha2! We used the extra days to iron out some annoying bugs, such as the crash on first run some users experienced, and made the sync-to-core process much faster.
More features include:
- Sane first-run layout of dockwidgets
- Various UI enhancements
- Buffer switching via mousewheel (thanks Ian "eean" Monroe for the patch!)
- Redirection of notices and server messages to the status buffer or the current buffer
It's always amazing how easily one can be destracted from learning...
Despite having an exam next tuesday I've spent most of this day on fixing bugs and tweaking things for -alpha2. Sput's already fixed one of the major bugs: the client crash during first run network setup. So what to expect from -alpha2? Actually not much more than from -alpha1. :) Find a list of the fixes and features after the jump.
I just switched to universal binaries, so the Mac Client will be able to run on PPC Macs as well as on the new intel ones. Get it in the "Get Quassel!" section or right here.
Currently there is only the Client build. If you're interessted in precompiled Mac builds for the Quassel Core or the Monolithic Quassel, then please let me know.
It is finally here - quassel-0.2.0-alpha1, Quassel's long-awaited first public release! This is still an alpha version, so it still has some quirks, and it still lacks some features that may or may not be important for you. That said, we (the devs) have been using it as our main client for weeks now, and we are fairly happy with it, so it can't hurt to give it a try!
Only this release sets your computer on fire, eats your dog and is probably highly addictive.
Well, EgS speaking of 50 commits in January until the 17th. Turned out to be 125 commits until the end of the month, and another 55 commits in the eight days of February already... development speed is increasing, and we can now see the light at the end of the tunnel (and it's not a train coming at us). We are fighting some stability issues and we still need to fix a couple of things, but we are now very confident that we can release Quassel within the month!
This is not only my first post on Quassel IRC but my very first blog post at all.
I have to say that I'm pretty excited about what's happening in the last few weeks. The improvements on Quassel have been enormous. There've been already more than 50 commmits this month. Having just checked in Revision 353 and waiting for Sput's next big commit (which hopefully doesn't break anything - I'm always scared if someone says: dude I'm just reorganizing the multithreading in the core...), I'm having some leisure time, which I want to use tell you a bit about the current state of Quassel IRC.
2007 has come and gone, and now it is 2008. Last year has seen a lot of improvements in and around Quassel IRC, and we are now very close to the first releaseable version. In fact, we, the developers and some early testers/helpers/fans are running Quassel Cores on our servers to stress-test (and of course enjoy) them! We now mainly lack some features in the GUI and some improvements in internal structures to be able to release Quassel to the public.
And this is my resolution for 2008: Get Quassel IRC out of the door ASAP, and then continue to make this the bestest IRC client ever!