<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Quassel IRC blogs</title>
  <subtitle>Chat comfortably. Anywhere.</subtitle>
  <link rel="alternate" type="text/html" href="http://quassel-irc.org/blog"/>
  <link rel="self" type="application/atom+xml" href="http://quassel-irc.org/blog/atom/feed"/>
  <id>http://quassel-irc.org/blog/atom/feed</id>
  <updated>2008-03-04T23:40:34+01:00</updated>
  <entry>
    <title>rc1 will (hopefully) be the last Release Candidate... ever!</title>
    <link rel="alternate" type="text/html" href="http://quassel-irc.org/node/83" />
    <id>http://quassel-irc.org/node/83</id>
    <published>2008-07-08T00:35:29+02:00</published>
    <updated>2008-07-08T00:35:29+02:00</updated>
    <author>
      <name>Sputnick</name>
    </author>
    <summary type="html"><![CDATA[<p>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.</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>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.</p>
<p>Roughly around the same time, we'll also release a 0.3.0 version, so people willing to play with the new stuff can get proper releases as well. The 0.3 series will be considered a development branch. Future will tell if we stick with that (i.e. odd minors = devel releases, even minors = stable releases). We plan to put a lot of experimental and exciting stuff into 0.3, so this series will probably be alive for quite a while (while 0.2 will only see major bugfixes in the future, but no new features).</p>
    ]]></content>
  </entry>
  <entry>
    <title>Releasing a candidate</title>
    <link rel="alternate" type="text/html" href="http://quassel-irc.org/node/82" />
    <id>http://quassel-irc.org/node/82</id>
    <published>2008-07-03T14:20:44+02:00</published>
    <updated>2008-07-03T14:20:44+02:00</updated>
    <author>
      <name>Sputnick</name>
    </author>
    <summary type="html"><![CDATA[<p>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 <a href="/downloads">grab it while it's still steaming!</a></p>
    ]]></summary>
    <content type="html"><![CDATA[<p>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 <a href="/downloads">grab it while it's still steaming!</a></p>
    ]]></content>
  </entry>
  <entry>
    <title>Mac OS X nightlys back on track</title>
    <link rel="alternate" type="text/html" href="http://quassel-irc.org/node/80" />
    <id>http://quassel-irc.org/node/80</id>
    <published>2008-06-28T16:40:03+02:00</published>
    <updated>2008-06-28T16:40:03+02:00</updated>
    <author>
      <name>EgS</name>
    </author>
    <summary type="html"><![CDATA[<p>After all the hazzle that came with the switch from svn to git and qmake to cmake, I'm glad to tell you, that the nightly builds for Mac OS X are available again. Currently there are only Mac OS X nightlys for 0.2 but that is about to change soonish. Get them as usual at <a href="http://quassel-irc.org/nightly/macosx/" title="http://quassel-irc.org/nightly/macosx/">http://quassel-irc.org/nightly/macosx/</a></p>
    ]]></summary>
    <content type="html"><![CDATA[<p>After all the hazzle that came with the switch from svn to git and qmake to cmake, I'm glad to tell you, that the nightly builds for Mac OS X are available again. Currently there are only Mac OS X nightlys for 0.2 but that is about to change soonish. Get them as usual at <a href="http://quassel-irc.org/nightly/macosx/" title="http://quassel-irc.org/nightly/macosx/">http://quassel-irc.org/nightly/macosx/</a></p>
    ]]></content>
  </entry>
  <entry>
    <title>Quassel at ohloh</title>
    <link rel="alternate" type="text/html" href="http://quassel-irc.org/node/78" />
    <id>http://quassel-irc.org/node/78</id>
    <published>2008-06-17T12:09:29+02:00</published>
    <updated>2008-06-17T12:09:29+02:00</updated>
    <author>
      <name>Sputnick</name>
    </author>
    <summary type="html"><![CDATA[<p>Thanks to Flameeyes, we now have an <a href="http://www.ohloh.net/projects/quassel">official presence</a> at the very cool "Social Network for Open Source Developers" called <a href="http://ohloh.net">ohloh</a>. If you are a Quassel user, don't hesitate to stop by and show the world :)</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>Thanks to Flameeyes, we now have an <a href="http://www.ohloh.net/projects/quassel">official presence</a> at the very cool "Social Network for Open Source Developers" called <a href="http://ohloh.net">ohloh</a>. If you are a Quassel user, don't hesitate to stop by and show the world :)</p>
    ]]></content>
  </entry>
  <entry>
    <title>Switching to CMake</title>
    <link rel="alternate" type="text/html" href="http://quassel-irc.org/node/77" />
    <id>http://quassel-irc.org/node/77</id>
    <published>2008-06-17T12:06:07+02:00</published>
    <updated>2008-06-17T12:06:07+02:00</updated>
    <author>
      <name>Sputnick</name>
    </author>
    <summary type="html"><![CDATA[<p>After our switch to Git as our version control system, we now also have changed our build system from qmake to <a href="http://www.cmake.org">CMake</a>. 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.</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>After our switch to Git as our version control system, we now also have changed our build system from qmake to <a href="http://www.cmake.org">CMake</a>. 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.</p>
<p>So now we're back to CMake. You'll find build instructions in INSTALL.cmake (soon that will be moved to INSTALL). It has been tested on Linux, MacOSX and Windows. It is also much simpler than our old CMake-based build system, as CMake has evolved, removing the need for some of the ugly workarounds we had. Thanks to Flameeyes, we also finally have a "make install" that installs the binaries and .desktop files where they belong; soon to be followed by application icons. And last but not least, it's colorful and shiny :)</p>
<p>So if you happen to run buildscripts or similar, please migrate them over to the new build system, since we will be removing the qmake stuff in a few days!</p>
    ]]></content>
  </entry>
  <entry>
    <title>Switching to Git</title>
    <link rel="alternate" type="text/html" href="http://quassel-irc.org/node/76" />
    <id>http://quassel-irc.org/node/76</id>
    <published>2008-06-03T16:32:36+02:00</published>
    <updated>2008-06-03T16:32:36+02:00</updated>
    <author>
      <name>Sputnick</name>
    </author>
    <summary type="html"><![CDATA[<p>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? :)<br />
You can access the public repo as follows:<br />
<code>git clone git://git.quassel-irc.org/quassel.git</code></p>
    ]]></summary>
    <content type="html"><![CDATA[<p>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? :)</p>
<p>You can access the public repo as follows:<br />
<code>git clone git://git.quassel-irc.org/quassel.git</code></p>
    ]]></content>
  </entry>
  <entry>
    <title>Quassel IRC at Linuxtag (Berlin)</title>
    <link rel="alternate" type="text/html" href="http://quassel-irc.org/node/75" />
    <id>http://quassel-irc.org/node/75</id>
    <published>2008-05-27T01:27:13+02:00</published>
    <updated>2008-05-27T01:27:13+02:00</updated>
    <author>
      <name>Sputnick</name>
    </author>
    <summary type="html"><![CDATA[<p>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 <a href="http://amarok.kde.org">Amarok</a> booth again. If you happen to be at Linuxtag as well, don't hesitate to stop by at the booth and say hello!</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>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 <a href="http://amarok.kde.org">Amarok</a> booth again. If you happen to be at Linuxtag as well, don't hesitate to stop by at the booth and say hello!</p>
    ]]></content>
  </entry>
  <entry>
    <title>β</title>
    <link rel="alternate" type="text/html" href="http://quassel-irc.org/node/74" />
    <id>http://quassel-irc.org/node/74</id>
    <published>2008-05-15T17:31:21+02:00</published>
    <updated>2008-05-15T17:31:52+02:00</updated>
    <author>
      <name>Sputnick</name>
    </author>
    <summary type="html"><![CDATA[<p>Yes, we can finally announce the release of Quassel's very first <a href="/downloads">beta</a>! 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...<br />
<a href="/node/74">Read on</a> for the release notes for quassel-0.2.0-beta1!</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>Yes, we can finally announce the release of Quassel's very first <a href="/downloads">beta</a>! 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...</p>
<p><a href="/node/74">Read on</a> for the release notes for quassel-0.2.0-beta1!</p>
<p>There have been many bugfixes, some performance improvements and some new features. Most notably: The bufferviews are now fully customizable! You can create and edit views using the settings dialog (F7) -&gt; General -&gt; Buffer Views. Buffers can be reordered using drag'n'drop, you can hide inactive buffers and much more. All your views will be stored on the core, so you can share them amongst your clients. Please note that there currently is one known bug where new buffers will not always be shown in custom views. They are visible in the "All Buffers" view though and can be dragged from there into custom views.</p>
<p>Also nice to know is that we have now a flood protection (throttling your messages in order to prevent you from being kicked from the network), and we have fixed the huge lag that you might have experienced on some networks.</p>
<p>And now, <a href="/downloads">get it while it's hot!</a></p>
<p>Have fun,<br />
~ Sputnick</p>
    ]]></content>
  </entry>
  <entry>
    <title>What&#039;s going on?</title>
    <link rel="alternate" type="text/html" href="http://quassel-irc.org/node/73" />
    <id>http://quassel-irc.org/node/73</id>
    <published>2008-04-24T16:04:55+02:00</published>
    <updated>2008-04-24T16:04:55+02:00</updated>
    <author>
      <name>Sputnick</name>
    </author>
    <summary type="html"><![CDATA[<p>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!</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>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!</p>
<p>We have put the 0.2.x branch in feature freeze, since we believe that Quassel IRC is now featureful enough to be usable. We plan to release a beta soon, followed by an RC and the final hopefully not too far in the future.</p>
<p>While we keep using and testing and fixing 0.2.x, we have started work on the 0.3 branch (which is not trunk yet, since we don't want to screw up the people keeping current with svn builds). This branch will include a complete new message handling architecture on the client side, based on Qt's MVC classes. This will allow us to implement much more flexible buffers (e.g. containing merged contents from multiple channels/queries, a highlight buffer and more), and it should also be much more efficient RAM-wise. We will have yet to see how efficient that turns out to be speed-wise though...<br />
This architecture will enable us to finally start real work on the famous new ChatWidget, which will just be a view on the MessageModel (or various filtering proxy models).</p>
<p>Another point on the agenda for 0.3 is the long-awaited plugin interface, though we are not sure yet how extensive this will be - if we manage to implement a full-flegged scripting interface in the not too distant future, or if we'll only provide a few hooks for simple plugins as a temporary work-around...</p>
<p>So while our commit count seems to be down, and our channels are a little bit more dormant than usual, rest assured that a lot of good stuff is going on behind the scenes :)</p>
<p>Back to work.<br />
~ Sput</p>
    ]]></content>
  </entry>
  <entry>
    <title>Releasing the (hopefully) final Alpha for Quassel 0.2.0!</title>
    <link rel="alternate" type="text/html" href="http://quassel-irc.org/node/71" />
    <id>http://quassel-irc.org/node/71</id>
    <published>2008-04-09T21:27:23+02:00</published>
    <updated>2008-04-09T22:14:07+02:00</updated>
    <author>
      <name>Sputnick</name>
    </author>
    <summary type="html"><![CDATA[<p>It is with great pleasure that we announce <a href="/downloads">immediate availability</a> 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.<br />
For a more detailed list of important changes, <a href="/node/71">read on</a>!</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>It is with great pleasure that we announce <a href="/downloads">immediate availability</a> 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.</p>
<p>For a more detailed list of important changes, <a href="/node/71">read on</a>!</p>
<p><strong>Bugfixes:</strong></p>
<ul>
<li>Stopped quasselcore from potentially filling up your database with millions of strings when receiving invalid CTCP</li>
<li>A saner autowho implementation avoids throttling when sending messages to some networks, removing that annoying send lag you might have experienced</li>
<li>Font issues (garbled fonts, wrong formatting...) have been fixed</li>
<li>Finally allow parallel makes (make -j)</li>
<li>Made the core run on Windows[tm] as well</li>
<li>Made Quassel compile and run on MacOSX 10.4 (Tiger)</li>
</ul>
<p><strong>Features:</strong></p>
<ul>
<li>Custom highlights</li>
<li>Lots of UI tweaks</li>
<li>QuasselTopia compiles and sorta runs again... well, this is still highly work-in-progress and probably breaks again soon enough.</li>
</ul>
<p>We will now work on finalizing the feature list and removing the last outstanding issues for Quassel's first beta release, which we expect to release in a couple of weeks.</p>
    ]]></content>
  </entry>
  <entry>
    <title>YAQIA!</title>
    <link rel="alternate" type="text/html" href="http://quassel-irc.org/node/69" />
    <id>http://quassel-irc.org/node/69</id>
    <published>2008-04-01T13:42:01+02:00</published>
    <updated>2008-04-01T13:42:01+02:00</updated>
    <author>
      <name>Sputnick</name>
    </author>
    <summary type="html"><![CDATA[<p>We've released Yet Another Quassel IRC Alpha! Besides various bugfixes (the nick selector works again!), <a href="/system/files/quassel-0.2.0-alpha4.tar.bz2">quassel-0.2.0-alpha4</a> brings you some real nice new features:</p>
<ul>
<li>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...</li>
<li>Server passwords work now. Just enter them in the server edit dialog (Settings -&gt; General -&gt; Networks -&gt; Edit Server).</li>
<li>Highlighted messages now make your systray icon flash and/or display a shiny bubble. Configurable under Settings -&gt; Behavior -&gt; General.</li>
</ul>
<p>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.</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>We've released Yet Another Quassel IRC Alpha! Besides various bugfixes (the nick selector works again!), <a href="/system/files/quassel-0.2.0-alpha4.tar.bz2">quassel-0.2.0-alpha4</a> brings you some real nice new features:</p>
<ul>
<li>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...</li>
<li>Server passwords work now. Just enter them in the server edit dialog (Settings -&gt; General -&gt; Networks -&gt; Edit Server).</li>
<li>Highlighted messages now make your systray icon flash and/or display a shiny bubble. Configurable under Settings -&gt; Behavior -&gt; General.</li>
</ul>
<p>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.</p>
    ]]></content>
  </entry>
  <entry>
    <title>Nightly Snapshots</title>
    <link rel="alternate" type="text/html" href="http://quassel-irc.org/node/68" />
    <id>http://quassel-irc.org/node/68</id>
    <published>2008-04-01T13:30:55+02:00</published>
    <updated>2008-04-01T13:30:55+02:00</updated>
    <author>
      <name>Sputnick</name>
    </author>
    <summary type="html"><![CDATA[<p>We now provide nightly <a href="/nightly/source">source tarballs</a>, as well as a <a href="/nightly/linux">statically linked core</a> for Linux, MacOSX <a href="/nightly/macosx">client binaries</a> and <a href="/nightly/windows">Windows binaries</a>. 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, <a href="/nightly">here</a> they are :)<br />
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 <a href="/downloads">download page.</a></p>
    ]]></summary>
    <content type="html"><![CDATA[<p>We now provide nightly <a href="/nightly/source">source tarballs</a>, as well as a <a href="/nightly/linux">statically linked core</a> for Linux, MacOSX <a href="/nightly/macosx">client binaries</a> and <a href="/nightly/windows">Windows binaries</a>. 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, <a href="/nightly">here</a> they are :)</p>
<p>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 <a href="/downloads">download page.</a></p>
    ]]></content>
  </entry>
  <entry>
    <title>Static alpha3 core for Linux</title>
    <link rel="alternate" type="text/html" href="http://quassel-irc.org/node/67" />
    <id>http://quassel-irc.org/node/67</id>
    <published>2008-03-17T18:49:23+01:00</published>
    <updated>2008-03-17T18:49:23+01:00</updated>
    <author>
      <name>Sputnick</name>
    </author>
    <summary type="html"><![CDATA[<p>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 <a href="/downloads">download page</a> you'll now find an experimental core to try out even on servers without Qt.</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>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 <a href="/downloads">download page</a> you'll now find an experimental core to try out even on servers without Qt.</p>
<p>Note that this is highly experimental, since certain features seem to require a compatible shared glibc installed. Also on one of my test systems, charset encodings don't work, because iconv cannot be used even though it is installed... so please test it, and if anything is strange, please report.</p>
    ]]></content>
  </entry>
  <entry>
    <title>quassel-0.2.0-alpha3 has landed!</title>
    <link rel="alternate" type="text/html" href="http://quassel-irc.org/node/66" />
    <id>http://quassel-irc.org/node/66</id>
    <published>2008-03-16T22:45:43+01:00</published>
    <updated>2008-03-16T22:45:43+01:00</updated>
    <author>
      <name>Sputnick</name>
    </author>
    <summary type="html"><![CDATA[<p>We are pleased to announce the immediate release of <a href="/system/files/quassel-0.2.0-alpha3.tar.bz2">alpha3</a>! 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.<br />
As a bonus feature, you'll get an all new topic widget that displays mIRC-style formatting, and various other GUI tweaks.<br />
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 :)<br />
So <a href="/system/files/quassel-0.2.0-alpha3.tar.bz2">get it</a> while it's hot! Updated distro packages and precompiled binaries will soon be available on the <a href="/downloads">download page</a>.</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>We are pleased to announce the immediate release of <a href="/system/files/quassel-0.2.0-alpha3.tar.bz2">alpha3</a>! 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.<br />
As a bonus feature, you'll get an all new topic widget that displays mIRC-style formatting, and various other GUI tweaks.</p>
<p>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 :)</p>
<p>So <a href="/system/files/quassel-0.2.0-alpha3.tar.bz2">get it</a> while it's hot! Updated distro packages and precompiled binaries will soon be available on the <a href="/downloads">download page</a>.</p>
    ]]></content>
  </entry>
  <entry>
    <title>CeBIT Day One</title>
    <link rel="alternate" type="text/html" href="http://quassel-irc.org/node/65" />
    <id>http://quassel-irc.org/node/65</id>
    <published>2008-03-04T23:40:34+01:00</published>
    <updated>2008-03-04T23:40:34+01:00</updated>
    <author>
      <name>Sputnick</name>
    </author>
    <summary type="html"><![CDATA[<p>Hi there,<br />
blogging live from CeBIT, Hanover, Germant, Worls'd largest IT fair :) This time I am not promoting Quassel, but I am part of the <a href="http://amarok.kde.org">Amarok</a> 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:</p>
<ul>
    ]]></summary>
    <content type="html"><![CDATA[<p>Hi there,</p>
<p>blogging live from CeBIT, Hanover, Germant, Worls'd largest IT fair :) This time I am not promoting Quassel, but I am part of the <a href="http://amarok.kde.org">Amarok</a> 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:</p>
<ul>
<li>World's largest IT fair is unable to provide internet access during the day</li>
<li>Booth parties rock! :)</li>
<li>If you are looking for us: Hall 5, Booth E61/3</li>
<li>Pizza delivery directly to the booth works :)</li>
</ul>
<p>So much for now, hoping to get internet access tomorroy night at some point again :)</p>
<p>~ Sput</p>
    ]]></content>
  </entry>
</feed>
