Please read this, even if you've been requesting reviews forever....
this is from the perspective of those of us reviewers who are overloaded
with review requests.. help us streamline the process!
step 2 is OPTIONAL depending on if the reviewer (such as myself)
actually reads his bugmail.. bugmail contains all the information in
step 2 by default.
1) Add the reviewer to the CC of the bug, and say "CC'ing <reviewer> for
a review"
(if the reviewer doesn't want the spam, then they can just turn it off
with bugzilla bugmail prefs)
2) send mail to the reviewers and CC [EMAIL PROTECTED]
2a) Explain the component and/or the fix in the *subject* of the
message, such as "need review for plugins bug" or "need imap crash bug
review"
2b) Explain briefly what the *fix* is, i.e. "checking for null
pointer", or "redesigning layout so frame construction happens in
reverse order" so that reviewers understand the scope of the fix...if
it's just a null-pointer check, I'll sr= it in a second, no matter what
component it is.
2c) Be sure to include *the URL of the bug*- Why? Even if the bug
is NOT in my area but there is a LINK to click on, then I am 10x more
likely to at least look at the bug. If the message does not contain the
url, I'll often put it off until later.
A tired reviewer,
Alec
