KDE 3.5.9 has been released. “The KDE Community today announced the immediate availability of KDE 3.5.9, a maintenance release for the latest generation of the most advanced and powerful free desktop for GNU/Linux and other UNIXes. The most important changes have been made to the KDE-PIM applications, including the KMail email client, KOrganizer, a planning application and other components.”
Wow, well they are patching kde 3.5 which is nice but that didn’t stop them from closing my bug report with no reason given.
http://bugs.kde.org/show_bug.cgi?id=140530
” What |Removed |Added
———————————————————————- ——
AssignedTo|kwin kde org |kwin-bugs-null kde org”
I presume kwin-bugs-null is a way to drop the bug into a black hole.
The bug still shows as open, unconfirmed.
FWIW, I think I’ve seen this myself. I keep my kicker panel located at the top, with auto hide enabled, at 93% length.
I usually see this bug a lot more often when I have a lot of browser windows open.
Sometimes, the panel just relocates back to the bottom, but I can’t unhide it. I’ll have to fix it by opening up a term and re assigning the panel via Kcontrol.
I’ve seen it on SuSE and PCLoS.
I added to your bug report over there.
Edited 2008-02-20 02:03 UTC
No you are misleaded “kwin-bugs-null kde org” doesn’t mean the bug is assigned to a black hole. This is a work around some limitations of bugzilla (or at least the version runned by KDE), when bugs are created for a “product”, they are assigned to a default person (usually the maintainer), but if there is a team working on the “product”, other members of the team might want to be warned that a new bug has been entered. The only solution to do that is to follow the activity of the “default person”, the problem is that you will receive a mail for all of his bugzilla activity. That’s why there is those “PRODUCE-bugs-null kde org” addresses. Now I guess the change from “kwin kde org” to “kwin-bugs-null kde org” was probably made to avoid sending bugs mail to the mailing list, but still have the possibility to easily follow activity on the kwin bugs reports.
Really? This is what I get: KWin default assignee
Maybe I missed something.
A maintenance release for the “latest generation” ? Isn’t KDE 3.x the previous generation, with KDE4 having been released fairly recently?
I know that it is horribly confusing. But I believe that the official line is that although KDE 4.0.0 was released to the accompaniment of world wide release celebrations, KDE4 has not been released yet. KDE4 will be released this summer when KDE 4.1.0 comes out. It’s bizarre and confusing. One would imagine that core KDE devs view it as very simple and straightforward, however, and expect it should all be intuitively obvious to all of us.
Interesting take on it. I am even more confused after looking at the release announcements for 3.5.9 and 4.0.1.
3.5.9
now 4.0.1
So 3.5.9 is the most advanced for *nixes and 4.0.1 is the most advanced in general?
Regardless I am glad to see the continuing support for the KDE which I consider the latest stable release of KDE.
This is a simple a typo, most likely the result of using copy/paste from previous release annoncments.
Hmmm. First OSAlert readers were confused and angry that KDE developers put a internet gun to their head and made them run their distributions’ fist (and somewhat buggy (irregardless of the very real KDE 4.0.0 gotchas.) KDE 4.0.0 packages. Now they’re confused and angry that there was another KDE 3 release. Oddly enough some of comments with the highest number of ‘+’s explained this rather well:
– KDE 4.0.0 is a singular release of KDE 4. It is what it is, may eat your children, but isn’t the whole of KDE 4. (Think ‘one of a subset’.)
– KDE 3.5 will see periodic releases, if for no other reason that there are large institutional installs of KDE 3.5, and distros still shipping KDE 3.5. These folks, along with KDE developers tend to need and produce bug fixes which get rounded up into further point releases.
– The KDE 3.5 series allowed selective introduction of new features (see KDEPIM in 3.5.9) if they were deemed to have already received wide exposure and posed little chance of major regression.
That actual interesting question is: “Now that the first post KDE 4 release of the KDE 3.5 series is out how deeply frozen is the KDE 3.5 series?” Personally I suspect (and hope) its way deep in the icebox, and that 3.5.10 will be months off and a roundup of critical distro produced fixes and security fixes and that’s it…
On the KDE 4 front it looks like the worst sins of the KDE 4 panel have been fixed, and will be available for KDE 4.0.2.
See:
http://techbase.kde.org/Projects/Plasma/4.0.2_Backporting_Session
(Thank goodness.)