Development Testing (was: Re: audio hardware)

[Cory K.]

D. Michael McIntyre wrote:
> On Monday 17 September 2007, Cory K. wrote:
>   
>> Off Topic:
>> I'd also like to say that our users are also responsible for how a
>> release turns out. You must test the development releases to make sure
>> things work and report what doesn't. Fixing things after the fact
>> becomes more of an issue than before release.
>>     
>
> Speaking from the project, rather than distro level, I'd still like to echo 
> those comments wholeheartedly.  Rosegarden's pre-release testing sucks.  
> We're too close to it to be good testers, and most users stick with whatever 
> comes with their distro, which is usually a version or more out of date to 
> boot.
>   
So I'm guessing you're a Rosegarden dev?
> Looks like we're about to lose another race with Gutsy.  We're trying to 
> release by the end of this month, and Gutsy will probably be frozen or 
> released by then.  I haven't looked at your schedule, but people are making 
> noises like Gutsy is already mostly usable, so I figure it's going to come 
> out stuck with our last release.  Again.
>   
Yes. This is a pain I agree but is the system we (the Ubuntu Studio
project) work with. :( We really try to work with upstream as much as we
can. Thing that slows us down sometimes is that its important for us to
sync from Debian. Kinda a "trickle-down" effect. Though, it can often
mean that by the time it hits Ubuntu the app is a little old.

I do feel that old isn't bad and that people need to stop wanting
"bleeding edge" with everything.
> This whole production model is a pain in the ass.  Oh well.  At least the pay 
> is great, right?  Plus all the fame and glory when people on the street know 
> your name, and the project(s) you work on, and get you to sign autographs 
> everywhere you go.
>   

Yes. We're all geeky rock-stars. :D