I think tracking and investigating is all of our responsibility. QA definitely has a role to play and I think we've been playing that role to a certain extent. We don't always have the skills, knowledge, experience, or time to help but we always try and we are always willing to learn. We rely on Release Management to keep us apprised of what's important and we rely on developers to help us understand the code, tools, and testcases.
Having a Bugmaster will certainly improve things but I don't think it eliminates the necessity, nor the desire for this collaborative dynamic. ----- Original Message ----- From: "Dave Mandelin" <dmande...@gmail.com> To: dev-platform@lists.mozilla.org Cc: "Dave Mandelin" <dmande...@gmail.com>, dev-platform@lists.mozilla.org Sent: Thursday, August 30, 2012 6:13:33 PM Subject: Re: The current state of Talos benchmarks On Thursday, August 30, 2012 2:54:55 PM UTC-7, Ehsan Akhgari wrote: > Oh, sorry, I needed to ask my question better. I'm specifically > wondering who needs to track and investigate the regression if it > happened on a range of, let's say, 5 committers... Ah. I believe that's a job for a bugmaster, a position that we don't have filled at the moment. We need one. Perhaps one or more people in QA can step into part of that role, possibly temporarily. Otherwise, it seems we just have to share the pain. Bisecting changesets is not necessarily an enjoyable job but it is a necessary one. I would suggest that sheriffs pick one of the 5 committers and ask that person to bisect the change and try not to pick the same person repeatedly (unless that person keeps landing the regressions!). Dave _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
