Closed Bug 750736 Opened 12 years ago Closed 11 years ago

SecReview: (minotaur) [meta] Implement a script debugger

Categories

(mozilla.org :: Security Assurance: Review Request, task)

Product:
mozilla.org
Component:
Security Assurance: Review Request
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: curtisk, Assigned: mgoodwin)

References

Details

(Whiteboard: [completed secreview]) 

SecReview tracking bug
Actions regarding the review of the dependent bug should be tracked here.
Whiteboard: [pending secreview][start mm/dd/yyyy][target mm/dd/yyyy] → [in-progress secreview][start mm/dd/yyyy][target mm/dd/yyyy]
Depends on: 755513
We should get the standard questions answered, even if we are not going to do a big team review:
1) Who is/are the point of contact(s) for this review?
2) Please provide a short description of the feature / application (e.g. problem solved, use cases, etc.):
3) Please provide links to additional information (e.g. feature page, wiki) if available and not yet included in feature description:
4) Does this request block another bug? If so, please indicate the bug number
5) This review will be scheduled amongst other requested reviews. What is the urgency or needed completion date of this review?
6) To help prioritize this work request, does this project support a goal specifically listed on this quarter's goal list?  If so, which goal?
7) Please answer the following few questions: (Note: If you are asked to describe anything, 1-2 sentences shall suffice.)
7a) Does this feature or code change affect Firefox, Thunderbird or any product or service the Mozilla ships to end users?
7b) Are there any portions of the project that interact with 3rd party services?
7c) Will your application/service collect user data? If so, please describe
8) If you feel something is missing here or you would like to provide other kind of feedback, feel free to do so here (no limits on size):
9) Desired Date of review (if known from https://mail.mozilla.com/home/ckoenig@mozilla.com/Security%20Review.html) and whom to invite.
Whiteboard: [in-progress secreview][start mm/dd/yyyy][target mm/dd/yyyy] → [in-progress secreview][start mm/dd/yyyy][target mm/dd/yyyy][needs info]
(In reply to Curtis Koenig [:curtisk] from comment #1)
> We should get the standard questions answered, even if we are not going to
> do a big team review:

We have actually had team reviews for this; the latest being: https://wiki.mozilla.org/Security/Reviews/Firefox/RemoteDebug

This is currently open awaiting a change identified during previous secreview work which Nick Fitzgerald is currently working on (see bug 755661).  I'll change the dependencies to make this more obvious.

Thanks
Depends on: 755661
Ah ok, so under a differnt title, can we resolve this bug as fixed then?
Yea, I'm OK with this; I'm not going to lose sight of bug 755661 as I reported it.
does this bug still require the [needs info] tag or what is going on here?
Flags: needinfo?(mgoodwin)
Whiteboard: [in-progress secreview][start mm/dd/yyyy][target mm/dd/yyyy][needs info] → [in-progress secreview][start mm/dd/yyyy][target mm/dd/yyyy]
This bug still depends on https://bugzilla.mozilla.org/show_bug.cgi?id=755513, but I don't think there is a plan to start implementing that yet.  Bug 755661 is fixed.
Feature bug is closed, group reviews have happened; closing secreview.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Flags: needinfo?(mgoodwin)
Resolution: --- → FIXED
Whiteboard: [in-progress secreview][start mm/dd/yyyy][target mm/dd/yyyy] → [completed secreview]
You need to log in before you can comment on or make changes to this bug.