Message: previous - next
Month: April 2012

Re: [trinity-devel] kpowersave now working without HAL

From: Darrell Anderson <humanreadable@...>
Date: Sun, 15 Apr 2012 17:55:18 -0700 (PDT)
> There are many distributions that do not provide HAL, or
> worse on which HAL actually breaks basic functionality (i.e. keyboards/mice
> suddenly don't work, etc.).  Sounds like we need to get R14.0
> out the door ASAP, even if it it slightly buggy, so that we can start working
> on more fundamental problems.
> Thoughts are welcome!

From where is this idea derived that we need to get R14 out the door ASAP? Suddenly we have to push a "slightly" buggy release? Why? Who is keeping score?

My calendar says April, not May.

Which fundamental problems? Like a few hundred bug reports?

How are we supposed to test this new hardware support when half of us can't build a complete package set?

Are we again pushing a buggy release? Seems we have seen that story, what? twice now?

Trinity is not "slightly" buggy. Trinity is buggy. Many bug reports need resolution. Many build issues need attention.

Trinity is broken with respect to building with gcc 4.7.

If we spent time as a team addressing the bug tracker we could release a non buggy R14. If we spent time as a team helping and coaching one another we'd have fewer bugs. Almost every day David and I post build issues and bugs. We receive no meaningful help. We resign ourselves to posting the issues to the bug tracker and there the problems sit without resolution or motion.

We likely could resolve all build issues in less than a week if everybody pitched in and helped. We likely could resolve dozens of bug reports if everybody pitched in and helped.

And then, maybe, we actually would have stable foundations on multiple distros to thoroughly test the new hardware support system.

Please don't rip HAL support. Not everybody is using bleeding edge distros --- let people build whichever mechanism they want through build options.

Please don't push a buggy R14.