[I posted this on .general previously, but got no replies... reposting
here where more people who can answer might live. This version is edited
to remove excess junk and make the actual question more prominent]
Mitchell Baker wrote:
>
> Got questions about the "super-review" process - what it's for, how it
> works, what to expect? You may find answers in this new Code Review
> FAQ. It's not yet linked to from other docs, but it will be shortly.
That FAQ is great!
I have a specific question that's vaguely related to this.
I reported a bug and shortly afterwards provided a patch for it; I also
went on irc to request r= on the patch. During this process the bug was
reassigned to someone for evaluation of the proposed behavior; I got the
r=, but conditional on the bug owner's approval of the behavior change.
My question is: is there anything that I can or should do to facilitate
the incorporation of this patch? Is mailing the new bug owner to ask for
a quick answer inappropriate? (as of now, the bug is still NEW with no
comments from its new owner).
The bug remains targetted at mozilla1.0 based on my initial nomination
when I submitted the bug, before writing the patch, but it seems to me
that having a patch that's reviewed and all but ready to go should be
able to get in sooner than that. The patch is the *deletion* of approx
13 lines and nobody yet has actually disagreed with the behavior. I've
changed my nomination to 0.9.2... but will anybody notice the nomination
when the target milestone is already set?
It's a tiny bug and I don't care about it as much as the length of this
email would indicate... but it is my first patch ever and I'm also
trying to get a feel for the mozilla process in the hopes of providing
more patches in the future.
So - any suggestions?
Stuart.
PS Specifics left out of the body of the email to encourage general
answers for the future, but for reference, the bug is
http://bugzilla.mozilla.org/show_bug.cgi?id=78206
