> > I ask because I submitted many
> bug reports and most of them remain open. A
> > handful are critical if I am to migrate from KDE
> 3.5.10 to Trinity. If I
> > had to whittle my list to a few hopefuls for 3.5.13:
> >
> > 293   Kde-config Incorrectly Creates a
> Profile Folder in the System root
> > directory
> > 388   KDESU Dialog Box Behavior
> > 393   Incorrect kdesu Behavior When
> Opening Kate
> > 394   Problems with DCOP After Using
> kdesu
> > 296   New Trinity Profile Error
> Messages
> > 335   Konqueror Icon Activation Effect
> > 389   Activation Effects
> > 385   Unmounted removable device icons
> do not appear on the desktop
> > 303   Safely Unmount does not always
> remove the icon from the desktop
> > 258   ksmserver: Logout confirmation
> fadeaway is too slow with older
> > hardware
> >
> > Some or all of these bugs might have been resolved
> without the developer
> > being aware of a bug report. Building and testing the
> packages will go far
> > to help and might be the only way to confirm the bug
> is resolved. I hope
> > to attempt building soon, which is why I started this
> thread, but did not
> > want to start if development was still in arrears.
> >
> > Darrell
> 
> Some of the kdesu bugs may have been fixed, but
> unfortunately no one has
> had a chance to work on the others AFAIK.  We are
> after all only human,
> with day jobs and other responsibilities to get in our way.
> ;-)
> 
> I have decided to go ahead with the release in the hopes
> that the
> significant improvements may attract more developers, to
> avoid the project
> appearing dead, and to allow us to move to GIT (which may
> also help
> attract more developers).  This release is not perfect
> by any means, but
> it is still an improvement overall upon its predecessors.
> 
> Tim

Tim, no need to apologize. :) I have not participated in any testing all year because my own schedule prevented that. I predicted that when 3.5.12 was released. My schedule is starting to look like I might again be able to get involved as fall shifts into winter. I might not be able to help before the planned release date but sometime before year's end I expect to be able to help test building packages and test the software in action.

I understand the desire and reasons for releasing even if some serious bugs remain outstanding. That happens with any software project. I expect after the release that key developers will understandably want to disappear and rest for several weeks.

Hopefully thereafter the bug list receives serious attention. That was the plan after 3.5.12 until the shift to cmake happened.

I hope the wiki gets updated for transitioning to GIT. I haven't a clue how to migrate from SVN to GIT or how to keep my local tree current. :)

I look forward to 3.5.13. I continue reading stories about dissatisfaction with KDE 4, GNOME 3, Unity, etc. There are many users who want a full featured traditional desktop and do not want the overhead of KDE 4 or the non-traditional desktops of GNOME 3 and Unity. I believe Trinity will fill a void and will be well received if users believe there is active development.

I suspect reviewers of 3.5.13 will incorrectly compare Trinity to KDE 4. :( I don't know how to handle that misconception, but the 3.5.13 press release should reflect that Trinity is an alternate desktop and is not a competitor of KDE 4. The focus should be on traditional desktops and desktops intended for older and midweight hardware. Perhaps one method to avoid comparisions to KDE 4 is to drop all comments that Trinity is a continuation of KDE 3.5.10. Let Trinity stand on its own merits. Perhaps the 3.5.13 wiki could be posted and everybody involved here can post comments in this list to help ensure users and reviewers understand Trinity when they read the wiki and announcements.

Darrell