Closed Bug 10245 Opened 25 years ago Closed 24 years ago

Need a time stamp for Launch/Re-Launch

Categories

(SeaMonkey :: General, defect, P2)

Tracking

(Not tracked)

VERIFIED WONTFIX
Future

People

(Reporter: leger, Assigned: dp)

References

Details

(Keywords: perf, Whiteboard: [nsbeta3-])

Hey dp! Could ya make it so the Launch time and re-launch time are recorded in the console windows? Can you do something simliar for Mac and Linux too?
Priority: P3 → P2
Target Milestone: M9
Status: NEW → ASSIGNED
Will do!
Whiteboard: move to m10?
Target Milestone: M9 → M10
Jan I dont have time to do this for M9. So keep doing your old way.
Severity: critical → blocker
Whiteboard: move to m10? → [Perf]move to m10?
Putting on [Perf] radar...and moving to blocker...jpatel is leaving in a few weeks. We need this in ASAP please.
Severity: blocker → major
Target Milestone: M10 → M11
Downgrading to major since jan, you already have a way of measuring this.
Target Milestone: M11 → M15
Post beta. Dont have bandwidth to work on this. Please use your existing method to determine the launch times.
QA Contact: leger → bsharma
Updating QA contact and putting paw on cc list so we can all watch :-)
Keywords: perf
Bulk add of "perf" to new keyword field. This will replace the [PERF] we were using in the Status Summary field.
removing extraneous perf tag
Whiteboard: [Perf]move to m10? → move to m10?
This depends on fixing nsStopWatch.
Whiteboard: move to m10?
Blocks: 11349
Target Milestone: M15 → M20
Putting on nsbeta3 radar. QA needs this to do PR3 perf testing.
Keywords: nsbeta3
Future.
Whiteboard: [nsbeta3-]
Target Milestone: M20 → Future
marking this wontfix since it seems thta no one cares about this any more. both the owner and reporter of this request have left the project. If someone reopens it reassign it to the proper component.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
Marking verified
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.