Quassel windows 7

Do not interrupt the upgrade process, otherwise your database may become corrupted! With that out of the way, please head on over to the downloads page to get yourself a fresh Quassel tarball, Windows installer or OSX package.

Or wait until the new version hits a distro near you! As always, feel free to join us in quassel on the Freenode IRC network if you have questions, or just want to talk to our friendly community. One final remark: As we have announced a few times now, the 0. But this it not the only change; behind the scenes, we have already been very busy modernizing the codebase, and we will merge a giant pile of changes into the master branch soon after branching out 0.

Going forward, Quassel will require a more recent toolchain, as well as system libraries; the baseline we have chosen for the time being is Ubuntu Thus, we decided to roll a second release candidate. Please see the updated ChangeLog for more.

Of course, the information and caveats mentioned in the release announcement for 0. Please head on over to the downloads page to grab the packages, or just click here:. We expect to do a final 0. Since so much work and changes went into this, this time we've decided to not only roll a release candidate, but also announce it publicly, so daring people can test things before final release.

Some caveats upfront: Both the database schema and the config file formats have been updated since 0. Quassel will automatically upgrade both once the new version is started for the first time, however no rollback is possible , so do make a backup! Also the upgrade may take a long time several hours if your database is un reasonably large, during which the core or mono client cannot be used. Nevertheless, the Quassel protocol between remote cores and clients still is backwards-compatible all the way down to 0.

While you may not be able to use all the newer features when connecting to older versions, things still work, and there is no need to upgrade both ends at the same time. This is also a call for translators. If you'd like to improve the localization of Quassel in your language, please head over to Transifex and contribute.

We'll merge back the updated translations shortly before final release of 0. Too many changes went into this release to be able to list them all have a look at the ChangeLog for a reasonable overview , but here are some highlights:. We're discontinuing the pseudo-static core, because creating static binaries that run on most platforms becomes increasingly fragile; bundling things like OpenSSL also introduces security risks, since the bundled version will not be updated with the system.

Additionally, our binary packages for OSX and Windows do not support the PostgreSQL database backend for the core due to limitations in our build environments, as well as lack of demand. Do let us know if you run into issues or regressions. Otherwise, we're expecting a final release in the coming weeks! NOTE: As announced several times already, 0. We'll significantly bump the build and runtime requirements for future releases in order to be able to modernize the code base.

Planned baseline for 0. Since it has been so long since the last release, we've decided to backport over a hundred commits worth of bugfixes and quality-of-life improvements to make upgrading worth your while. Go grab Quassel 0. Following our usual policy, we did not change the config file format nor the database schema compared to previous 0.

Thus, upgrading should be safe, and going back to a previous 0. Please have a look at the ChangeLog for a list of major things that went into this release, or check out the full list of commits since the last release. I'd like to use this opportunity to thank all contributors who keep Quassel alive and kicking despite my own lack of time, be it by providing pull requests, community support, translations, testing, or just being active in our IRC channels.

For this release, I want to particularly express my thanks to Janne "justJanne" Koschinski , Michael "mamarley" Marley and Shane "digitalcircuit" Synan for their timely support in handling the afforementioned vulnerabilities so professionally, both providing fixes and very thorough testing!

You rock! Next stop hopefully : Quassel 0. As announced, well, two years ago, this will be our last release still supporting Qt 4 and KDE 4. Then follow these EZPZ steps! Install it. Head over to this Gist and copy all the text. Set the checkboxes as you see in the below images. Now that you have done that, those lists should appear in your client, but probably not in the best places. Drag the title bars of the lists over to the right side.

You can drag lists onto other lists to create tabs. Branches Tags. Could not load branches. Could not load tags. Latest commit. Sput42 Bump version for release 0. Bump version for release 0. Git stats 4, commits. Failed to load latest commit information. Our main repository is located at Github. Contributions are very welcome, and preferred in the form of pull requests on Github.

The code you get from this repository is not intended for productive use. We sometimes break things or commit experimental features. However, we do try to keep the master branch in a usable and compiling state most of the time, as we have many users building from that despite all our disclaimers ;- Breakages usually get reported very quickly.

Please note however that we might upgrade configuration files or the database scheme without prior notice, and you may not be able to run older versions afterwards, as we don't support downgrades. You have been warned! This means that your client sometimes will require a certain core revision and the other way round.