On 04/11/2014 12:52 AM, Chris Peterson wrote:
Following up on our brainstorming sessions at the JS work week, I'd like to get your feedback on SpiderMonkey's priorities and document them in an ordered list that we can use as our "moral compass". :)Below I also propose a lightweight planning process to keep our focus trained on those project priorities. EXAMPLE LIST OF PROJECT PRIORITIES: 1. Chemspill bugs 2. sec-crit bugs 3. Release tracking bugs: Beta 4. Release tracking bugs: Aurora 5. Release tracking bugs: Nightly 6. topcrash bugs 7. Crashes and assertion failures 8. Misc regressions 9a. Firefox OS performance 9b. Games Initiative 9c. Dev Tools 9d. Firefox features and performance 9e. ES6 features 10a. Shumway 10b. Technical debt? 11a. Infrastructure debt like intermittent orange tests? 11b. sec-high bugs 11c. fuzzblockers? 11d. tsan bugs 11e. ES7 features?
Thanks for doing this priority list, at least this make things clear. :) I would suggest to amend it as follow: 6a. *reproducible* topcrash bugs 6b. fuzzblockers […] 9f. *non-reproducible* topcrash bugs- 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.
- fuzzblocker are often related to a crash / assertion which is too noisy. The fuzzblocker flag was made such as we know which crash should be fixed first, as the assertion is masking all other crash and breaks the quality of reports of our Security Team.
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?
https://wiki.mozilla.org/User:Cpeterson
Nice. I see two issues: - Javascript:JIT component seems to be missing. - Security bugs are not listed (which make sense on a public wiki) -- Nicolas B. Pierron _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
