On Wed, Dec 22, 2010 at 4:35 AM, Tom Parker <[email protected]> wrote: > I make tickets during the Auckland testing. It's quite hard work as I'm > fairly constantly interrupted by other testers.
Must concur with Tom here. It is damned hard, and it often breaks the dynamic of the testing session. IMHO, given how these testing meetings work, the summary email is the best we can get from the testing session itself. For things that I had seen as important, I'd try to repro (after the meeting) and document properly in a bug ticket. Sridhar is right, additional work is needed to ensure that maintainers read feedback about their activity. That does not need to be responsibility of the testers -- and can be taken on by other list members after the fact. cheers, m -- [email protected] [email protected] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff _______________________________________________ Testing mailing list [email protected] http://lists.laptop.org/listinfo/testing
