<div class="gmail_quote">On Mon, Jul 23, 2012 at 8:54 AM, Dan Milstein <span dir="ltr"><<a href="mailto:dan@wingu.com" target="_blank">dan@wingu.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Just wanted to make sure I followed the proper steps. Two weeks ago, I submitted a patch to an existing bug in twisted.mail.imap4, along with new tests + a description of what I did:<br>
<br>
<a href="http://twistedmatrix.com/trac/ticket/4080" target="_blank">http://twistedmatrix.com/trac/ticket/4080</a><br>
<br>
Is there anything else I should be doing, at this point?<br>
<br>
Thanks,<br>
-Dan<br></blockquote><div><br></div><div>Pretty much exactly what you are doing. Sadly it sometimes takes a while to get a ticket reviewed. </div><div><br></div><div>(this part of the process is sometimes frustrating, but it really does lead to quality software!)</div>
<div><br></div><div>The only thing(s) you can really do at this point is keep reminding people about your ticket, which you have done in this email.</div><div>You might also try the #twisted IRC channel on freenode to see if anyone is available (or will be available soon) to review this.</div>
<div><br></div><div>Once the patch/ticket is reviewed, you'll likely need to make a few changes (it's rare in my experience for a patch to go in on the first round of review) and then it'll need to be reviewed again. I have found that the faster you can get those changes submitted, the faster subsequent rounds of review happen, since the ticket is now on someone's mental "radar".</div>
<div><br></div><div>Thanks for contributing to Twisted!</div><div><br></div><div>Kevin Horn</div></div>