nospam@nospam wrote:
>
> Hi Stuart
>
> Not sure if this is the right forum either, but thanks for asking. Can
> you provide
> the bug number? That would help to get to an answer. In general, we
> do not want
> patches sitting around and getting no response. You didn't say how long
> the bug has
> look into it if you can provide a bit more info.
The bug number is in the PS at the bottom of my original message:
--- included text ---
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
--- end included text ---
It hasn't been long: the patch and review are both dated 05/17, so about
two weeks. It's not that I consider 2 weeks to be unacceptably long (and
I suggested myself that the patch was 0.9.2 material, not 0.9.1, so it
couldn't have gone in until now anyway) but rather that since nothing's
gone on in the last two weeks, there's no indication of whether anything
will *ever* happen.
Is there a procedure for asking that a milestone nomination be
re-evaluated? I added the mozilla0.9.2 keyword (removing the mozilla1.0
keyword I had previously added) but I don't know whether that alone will
make anything show up on anyone's radar, since the target milestone is
still set to 1.0.
I'm more than willing to go hunting for sr= and a= myself, but since my
r= is conditional I don't think it's worth doing that until the
conditions are met.
Thanks for taking a look at this :)
Stuart.
