Thanks Anthony. That is a lot for one person. Does anyone know if we have metrics for each component?
I think a community schedule could be created to help run through the triage backlog. Perhaps that effort could work with module & peers to help with the burden of triaging. cheers, Armen On 2014-04-17, 3:20 AM, Anthony Ricaud wrote: > On 16/04/14 16:36, Armen Zambrano G. wrote: >> What is the current process for triaging b2g bugs? >> I know that relman has flags for scheduled releases but I don't think I >> should be using those. >> >> I file bugs with steps to reproduce, build information and they get >> ignored for a long long time. Only some of my bugs get attention. >> >> Should I stop filing bugs? >> I'm trying to help find issues as early as possible to allow development >> not find them too late in the game. >> >> Looking forward to help, >> Armen >> > > This is an area where we're really bad. IMHO it should be up to module > owners to watch their components. I'm watching the Dialer component but > I'm currently behind by 400 mails. If you filed any in that component, > you can cc me and I'll take a look. > > If longtime Gecko contributors have any tips on how to effectively watch > a component, I'm all ears. > > If you believe your bug is a show-stopper, you can mark it as > blocking-b2g: 1.3|1.4|2.0? . This will be triaged for sure. -- Zambrano Gasparnian, Armen (armenzg) Mozilla Senior Release Engineer https://mozillians.org/en-US/u/armenzg/ http://armenzg.blogspot.ca _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
