The KDE Project is pleased to announce the immediate availability of KDE 3.3 Beta 2. As another step towards the aKademy in late August, this release is named Kollege. This beta release shows astonishing stability, so the KDE team asks everyone to try the version and give feedback through the bug tracking system. For a list of new features skim over the KDE 3.3 Feature Plan. For packages, please visit the KDE 3.3 Beta 2 Info Page and browse the KDE 3.3 Requirements List. The Konstruct build toolset has been updated for this release. Please note that the kdepim, kdevelop and kdewebdev modules also compile on KDE 3.2 systems.

I looked at the release plan and I indeed think people will have to hurry. I don't know if the feature list it up to date but it *looks* like there are many many things to do, and there is very very little time.

No hurry. All features not within this beta will not be in the final. Their entries will be moved to a future KDE feature plan - some of the "todo" list may be in and only need to be set to state "done" though.

It's good to see that bugs.kde.org reports more bugs found then submitted. it seems that another 2000 bugs more appear on the kde buglist. this can also be blamed on the fact that many many new programs have been added. In general I think kde is very stable. we just need to get some important applications like kontact and kopete(voice+webcam?) past something we can label 1.0 and kde will rock!

I've been using CVS HEAD for couple of days, and so far KDE 3.3 looks very good - like new KDE releases always do! I was happy to find Joystick module in KControl, very nice! Now it would be fun to have OpenGL 3D games for KDE!

What I'm missing / hoping: Search in KDE Help Center and fixes in KBabel.

Search in help was dropped, because KDE changed to new documentation format during 2.x -series. I hope that forthcoming ht://dig search engine will be able to index and search application documentation, some people are working on this.

KBabel chokes constantly when searching translations. Somehow this starts on strings that do not have translation in the database. Please, please, Andrea, fix it :)

Other than these, KDE 3.3 Beta 2 is very stable and nice. I do not recommend running betas on production use, although this . Please test and send bug reports!

I hope some distro will make a livecd with beta 2 like Onebase did for beta 1.
Really, you KDE people should release an "official" live cd every alpha, beta or release candidate. That would be easier and more comfortable for everyone willing to test and report bugs.

Unfortunately not. :-( I didn't had time to do it properly, so instead of just putting it into kdewebdev, I delayed the inclusion.
Also a note about Quanta's VPL: it was already present in 3.2, but it is more advanced in 3.3, thanks to the KHTML Caret Mode II.

I've liked the 3.3 previews I've seen thus far, but KGet crashes when saving the file list. This means it'll crash when autosave is on or when you try to export it. Has this been fixed in this beta? I just want to know whether it's worth me upgrading, since this was my sole annoyance with beta1 and KDE takes a long time to compile.

Eh, creating a new account is a hassle, and I'll just get "Works for Me" or "Not a Bug" responses from the developers anyway, so it's really not worth the precious time it drains from everybody, right?

Yes, actually I've fixed many bugs in the various open-source projects I've helped with. Bugs are generally easy, because they're just minor errors in how you do things. It's features that are the hassle.

bug:81612 perhaps?
(The bugzilla search query form might be complex, but limiting the result to product "kget" and summaries containing "list" reduced the results to 12 entries, among which "kget crashes when saving transfer list" sounds dead on.)

Wondering if there is a chance to "push" old bugs to the front of the fixlist. There is a rendering bug in Konqueror present from KDE2 days (bug#: 32577) that seems like it has been forgotten - submitters every now and then confirm new versions that have this bug while there is absolutely no answer from the developers. Hope it's not due to a bug in Bugzilla ;-)