Create a "Core:Performance Regressions" component

RESOLVED WORKSFORME

Status

()

bugzilla.mozilla.org
Administration
RESOLVED WORKSFORME
12 years ago
7 years ago

People

(Reporter: bz, Assigned: marcia)

Tracking

Details

It would be nice to have a "Performance Regressions" component in Core for cases where we don't know what caused the perf regression.... see bug 332163 comment 8 for the motivation.

Comment 1

12 years ago
"A temporary place for bugs until someone figures out what the appropriate component is" is what a General component is for.  If there's a "Performance Regressions" component, people will:

a) think they can find perf regressions by searching in it
b) file "Firefox 1.5.0.1 is /so/ much slower than 1.5!" (or slower than 1.0, etc) bugs in it

There are occasional bugs in Moz App Suite component that are pretty clearly some Core issue, but the component specific component (Layout vs. Networking) is far from clear so a General component would be useful for other purposes (to me at least).  As long as the perf regression bugs get the appropriate people cc'd, they won't get lost.
There is no Core:General component.  If we had one, that might be fine for the purposes of perf regressions.

As for the relevant people being cced, that's a significant "if", imo.  It doesn't happen nearly often enough.
(Assignee)

Updated

12 years ago
Status: NEW → ASSIGNED
Yeah, Core:General would probably be good for other reasons as well.
(Assignee)

Comment 4

12 years ago
I can create Core:General if that is all that is needed here.

Comment 5

12 years ago
bug 332905 asks for core: needs triage

Comment 6

12 years ago
Core:General got created as part of 332905.  Is that sufficient or do we still want a separate Performance Regressions component?
Yeah, that's good enough.
Status: ASSIGNED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → WORKSFORME
Component: Bugzilla: Keywords & Components → Administration
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.