Age | Commit message (Collapse) | Author | Files | Lines |
|
https://www.mozilla.org/en-US/quality/bug-writing-guidelines.html
|
|
|
|
|
|
|
|
potentially code execution
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
instead of updating reviewboard
|
|
|
|
|
|
the status on the experimental UI
|
|
should be clearer about how to get the patch landed.
- Fixed t/009bugwords.t failure
|
|
should be clearer about how to get the patch landed.
|
|
|
|
|
|
|
|
attachment is created
|
|
review portion
|
|
|
|
|
|
direct people to servicenow
|
|
|
|
|
|
|
|
|
|
after filing
|
|
|
|
|
|
|
|
|
|
in new tabs, with bugzilla's experimental UI
|
|
|
|
|
|
page (13px)
|
|
|
|
|
|
|
|
resolution buttons
|
|
|
|
|
|
to obtain victim's GitHub OAuth return code
|
|
|
|
|
|
|
|
Security : Review" tickets instead of "mozilla.org : Security Assurance : Review Request" tickets
|