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!
It is with great pleasure that we announce immediate availability of what will probably/hopefully/may be the last and final alpha release before we go into the beta cycle. As usual, this alpha release brings you bugfixes and new features, UI tweaks and more goodies, and we highly recommend upgrading. Especially since we fixed a very nasty issue in Quassel Core... and yeah, the fonts should now be working as well :) Also, we can finally provide a precompiled Quassel Core and monolithic Quassel for Windows[tm], so you should now be able to use it without having access to a *nix server... And we don't forget the MacOSX Tiger users either and now provide a package that runs on both MacOSX 10.4 and 10.5.
For a more detailed list of important changes, read on!
We've released Yet Another Quassel IRC Alpha! Besides various bugfixes (the nick selector works again!), quassel-0.2.0-alpha4 brings you some real nice new features:
- The backlog is now dynamically replayed from the core. This means as you scroll further up in a buffer, new backlog lines will be automagically requested and displayed. This gives you the possibility to scroll up "infinitely", well, up to the point where you first entered that channel...
- Server passwords work now. Just enter them in the server edit dialog (Settings -> General -> Networks -> Edit Server).
- Highlighted messages now make your systray icon flash and/or display a shiny bubble. Configurable under Settings -> Behavior -> General.
This release also breaks the core/client protocol (again, and it won't be the last time), so both your core and client need to be alpha4 to work.
We now provide nightly source tarballs, as well as a statically linked core for Linux, MacOSX client binaries and Windows binaries. Please be aware of the fact that these binaries are generated automatically from current SVN HEAD, which means they might be in an untested and/or non-working state. We do not recommend using them until you know what you're doing, but since people kept asking for them, well, here they are :)
Please note that we still tweak and break the core/client protocol on a regular basis. This means that your client sometimes will require a certain core revision and the other way round. For example, the current nightly clients do not run with alpha4 cores. Both client and core will warn in this case, but you should be aware of that fact anyway (especially since downgrades of config files or the database are usually not possible, so using a client or core that is "too new" might require you to upgrade the other component as well! You'll find even more disclaimers on the download page.
Many people don't have Qt installed on their servers (even though the needed parts can be installed without X11), which makes using Quassel quite cumbersome. I have been looking into providing a static core (i.e. one that does not have external dependencies like Qt) for a while now, but on Linux, this is surprisingly hard. Anyway, on the download page you'll now find an experimental core to try out even on servers without Qt.
We are pleased to announce the immediate release of alpha3! This release contains many performance improvements, especially during core sync and backlog replay. Furthermore, buffer switches should now be much faster. Also, the sync-to-core process now is not only faster, but also much more reliable than in alpha2, where sometimes not all channels were synced.
As a bonus feature, you'll get an all new topic widget that displays mIRC-style formatting, and various other GUI tweaks.
Please note that we have broken both the client/core protocol and the database schema with this release. This means you cannot connect with an older client to an alpha3 core or vice versa. The database schema will be automatically upgraded once you run your shiny new core for the first time. Please note that after this upgrade, you will no longer be able to run a pre-alpha3 core with your database! As always, backups are recommended :)
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.