Testing Team

[Cory K.]

On 11/06/2009 04:15 PM, Jussi Schultink wrote:
> On Fri, Nov 6, 2009 at 10:54 PM, Cory K.<coryisatm at gmail.com>  wrote:
>    
>> Now, this might seem like I'm poo poo'in' on the idea a bit but hear me
>> out.
>>
>> To this point, generally, applications work in Studio. Bugs are filed
>> aginst apps and are usually taken care of by upstream. So, I would like
>> to know, with this idea there had to have been some inspiration.
>> Something that sparked this idea for you Eric. What was it?
>>
>> OS-wise, Studio does have a couple of bugs I really wanna see taken care
>> of this cycle. ie: *-menu, *-controls and *-settings. But aside from
>> that I'd like to know what would be the specific focus of testing that
>> procedures would be developed from?
>>
>>
>>      
>
> Hi, I think you are forgetting one of the most important things, the rt
> kernel. Its vital that this gets more testing than it does, and that we make
> this the best experience we can for our users. it also provides an entry
> point for new team members, as well as testing for regressions with video
> and wireless (and otherI) drivers with the<rt kernel. we seriously dont get
> enough testing, and as its a relatively easy task and needs a lot of people
> on a lot of different hw, then its a very useful team to have.
>    

Oh I'm not forgetting at all. I just want to hear specific ideas from 
Eric. ;)


-Cory K.