trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: March 2011

Re: [trinity-devel] Bugs, bugs, bugs

From: Kristopher Gamrat <pikidalto@...>
Date: Fri, 4 Mar 2011 14:33:56 -0500
 On Friday 04 March 2011 21:20:12 Darrell Anderson wrote:
When are bugs going to receive attention?
>
I don't eat my own dog food. Despite some enhancements, I continue using
KDE 3.5.10 rather than Trinity 3.5.12.

I expended a lot of energy last autumn packaging Trinity 3.5.12 for
Slackware 12.2. My personal schedule prevented further packaging efforts,
but now that I again have some time, I am not motivated to package for
recent releases. Why? There are many usability bugs that render Trinity
frustrating. Many of which do not exist in KDE 3.5.10.

We have a very small team. We started out with just two team members,
We have an expanded effort for development, and from what I've seen,
most (all?) of the extra team doesn't know C++ and Qt, which leaves
Tim to deal with the bugs himself during his limited free time. The
extra help is working on learning cmake to help move us away from
autotools.

If I had the time (and a new hard disk), I'd learn C++ and Qt to help
bug squashing, but having two days that "might" be "mostly" free and
"maybe" a couple hours on my other days is not enough to learn at a
fast enough speed to be of much use.

We don't have a stable 3.5.13 release anyway, so you already have the
latest stable 3.5.12 release. However, if you feel you can help squash
bugs, feel free to grab our code from svn, look through the code, and
submit patches on the bugtracker for the appropriate bug. If you can't
help, then try to recruit some C++/Qt people to TDE to help expedite
the process.

-- 
Kris
"Piki"
Ark Linux Webmaster
Trinity Desktop Environment Packager