The majority have NOT been converted, but the automake build system has been repaired for the remaining apps and therefore works perfectly with the latest versions of Autotools. The main ones that are production ready are: tqtinterface arts kdelibs kdebase Others have been converted but I am not using the CMake versions of them in the Debian/Ubuntu builds, so I cannot vouch for completeness/correctness of the build files. Calvin, how is our Wiki on this subject? Do you mind putting up some pointers? YES! Lots of bug fixes are in SVN; see http://trinitydesktop.org/patches/ for a taste of what is to come. Tim

Therefore use cmake for those four packages and automake for all others? 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

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

Thanks much. :) If you are running Trinity SVN on Slackware, which is what I use too (13.1), if you have the time would you run some simple tests on the bugs I listed? I hope to soon start testing the build process again and hopefully thereafter I can more thoroughly test the bugs. Darrell

--- On Sat, 10/22/11, /dev/ammo42 <mickeytintincolle(a)yahoo.fr> wrote: Thanks for checking. I know everybody is busy but would be nice if some of these bugs were quashed before release. Any possibility the official release could be pushed to Nov. 15 and some top/critical bugs get attention? If not then c'est la vie. Look forward to 3.5.13 anyway. :) Darrell

On Sun, Oct 23, 2011 at 10:35 PM, Timothy Pearson < kb9vqf(a)pearsoncomputing.net&gt; wrote: Forgive me if I missed something on this thread but I'm talking mostly from what I've saw in the most recent SVN releases: isn't it better to postpone due to what may be a lack of polish that might drive away users in the same way KDE 4 and GNOME have done recently? One of the problems I have noticed ever since I started using Linux is that desktop environment teams are extremely preoccupied about release dates more than what users will experience when using said environment, resulting in what ends up as a product in a bug ridden mess that distros have to fix themselves before packaging. Not doubting your judgement - or anyone's - on the release date, since you better than anyone have a better view of the project as a whole. Could it be in order to have small release updates (call it 3.5.13.1) over the 3.5.13 branch until 3.5.14 is released, in a way to address the bugs that are know to exist currently but can't make the release date? Otherwise they just get pushed further to what can be a good while. That would seem to me a good way to handle this situation. Best regards, Tiago

On Sun, Oct 23, 2011 at 11:06 PM, Timothy Pearson < kb9vqf(a)pearsoncomputing.net&gt; wrote: True enough ;) I had assumed that in some way, given the time it takes to release, it probably would be interesting to do more bug fix releases but probably the versioning could be improved? I mean after all Trinity already supports things that KDE 3.5.10 didn't, like RandR. Have you considered trying to gather some financial support from big distros to hire developers to help, since it seems to be some interest in having Trinity for enterprise related distributions? At least I got the impression that it could be possible to gather some support from what I've read for a few months now. Best regards, Tiago

On Sun, Oct 23, 2011 at 11:08 PM, Timothy Pearson < kb9vqf(a)pearsoncomputing.net&gt; wrote: There are some bugs I noticed but I have only compared with KDE 3.5.10. Jabber support in Kopete hasn't been working for me and I've noticed some bugs with KRandR that I need to better understand before filling a bug report. KNetworkManager also needs some bug fixing but it is actually working so that depends on the goals of the project for each release and, as you say, 3.5.12 doesn't compile on current distros, which is very bad. What's next, 3.5.14 or 3.6? Best regards, Tiago

On Mon, Oct 24, 2011 at 12:53 AM, Timothy Pearson < kb9vqf(a)pearsoncomputing.net&gt; wrote: Great, then whatever bugs are left may be fixed before 3.6 :) Sure, will do. Is there something to replace it? I may have a look at that since there's nothing really better than knetworkmanager AFAIK. Best regards, Tiago

On 23 October 2011 21:14, Timothy Pearson &lt;kb9vqf(a)pearsoncomputing.net&gt; wrote: +1 Let the Network Manager team settle out the API before we begin to port it. nm-applet is a good applet, has little overhead and will get a big weight off our backs. It integrates well with our gtk integration as well. I think this is the best way to go. Calvin

Le dimanche 23 octobre 2011, Timothy Pearson a écrit : mostly the as some and, --------------------------------------------------------------------- When will the three letters K D E be replaced by "TDE"? When will the project will have only QT in common with KDE? And TDE 2.0 would be better than 3.6, right? I talk when I can not even compile what I downloaded ... And then find the bugs, failing to be able to correct them! Good luck to everyone Patrick

On Oct 22, 2011 12:45 PM, "scrat" &lt;baho-utot(a)columbus.rr.com&gt; wrote: finish scratch built linux os, it is booting and I am preparing to build xorg then I will start again trinity. We will have tarballs for the release.

In article &lt;99fd35a15ce6d2d84aa5677d46ca781e.squirrel(a)vali.starlink.edu&gt;du>, Timothy Pearson &lt;trinity-devel(a)lists.pearsoncomputing.net&gt; wrote: Could I put in a special plea for bugs 552 and 422 please ? Both have patches and I can vouch that both patches work. Nick -- Serendipity: http://www.leverton.org/blosxom (last update 29th March 2010) "The Internet, a sort of ersatz counterfeit of real life" -- Janet Street-Porter, BBC2, 19th March 1996

In article &lt;CAJFUHyUF1uyYBreio=cPTWeDiiitek3oyLB8SKKs6nrb+na8Jw(a)mail.gmail.com&gt;om>, Calvin Morrison &lt;trinity-devel(a)lists.pearsoncomputing.net&gt; wrote: I saw the BTS notifications, thankyou very much Tim. Nick -- Serendipity: http://www.leverton.org/blosxom (last update 29th March 2010) "The Internet, a sort of ersatz counterfeit of real life" -- Janet Street-Porter, BBC2, 19th March 1996