On 4/11/14, 2:37 AM, Nicolas B. Pierron wrote:
- top-crash are not always coming with a clear STR, in such case we would mostly be wasting time at trying to reproduce something. The reproducible one should indeed be important as we are able to investigate them. On the other hand, the non-reproducible one should not block our work, while we are waiting for somebody to report an STR.
That's a useful distinction. A top-crash that is not actionable (e.g. no STR) is less important that a crash that is blocking other people (e.g. a fuzzblocker).
In Scrum terminology, the P1 bucket is like a Sprint Backlog ("fix now") and the P2 bucket is like a Product Backlog ("fix soon").I can understand that we might not want to set a time-frame to "fix soon", but after how many "skip" iterations of P2 should we lower its priority?
I don't think strict rules would be necessary. Every bug is unique. A P2 bug that goes unfixed for a long time hopefully means that the team is busy fixing P1 and P2 bugs they believe are more important. :)
chris _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
