<br><br><div class="gmail_quote">On Thu, Apr 15, 2010 at 7:38 PM, Kirill 'Big K' Katsnelson <span dir="ltr"><<a href="mailto:kkm@adaptiveai.com">kkm@adaptiveai.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I keep bring these up to the attention of the list to no avail for<br>
months! This is the last time I am bothered. There are two very real<br>
very creepy bugs in asterisk that I submitted patches for, and the<br>
patches are sitting there "ready for testing" month after month. Every<br>
time I post a message here about these patches I am getting responses<br>
like "thanks for reminding us," "how nice you are being persistent,"<br>
and... that ends the attention span.<br>
<br>
If anybody is interested, the patches are:<br>
<br>
<a href="https://issues.asterisk.org/view.php?id=16033" target="_blank">https://issues.asterisk.org/view.php?id=16033</a><br>
[patch] Autocreated peers not deleted when unregister explicitly, become<br>
zombies<br>
2009-10-08 07:06 lmadsen Status acknowledged => ready for testing<br>
<br>
<a href="https://issues.asterisk.org/view.php?id=16590" target="_blank">https://issues.asterisk.org/view.php?id=16590</a><br>
[patch] Monitor resumes recording after SIP transfer despite<br>
StopMonitor() having been called<br>
2010-01-13 09:19 lmadsen Status new => ready for testing<br>
<br>
I am dropping these off my monitoring list. If they are gone, they are<br>
gone. I will continue to maintain them privately for myself.<br></blockquote><div><br>While I can understand your frustration, giving up now would make all you've<br>done a total waste of time. You will have to keep updating your patches with<br>
every release to the end of time. You need to see it thru.<br><br>First of all, did you go in and test your fixes on 1.4 thru trunk? The developers<br>are obligated to do this before merging fixes into any particular release. And if<br>
it doesn't go smoothly, they might tend to let it drop to another day, when they<br>have the time to adapt the patch (which they may never have).<br><br>Next, did you test your patch in a rigorous manner? Can you prove there will<br>
be side effects? Show what you tested, and how.<br><br>Another tactic is reviewboard. For anything but trivial bug fixes, you might<br>post your diffs there, and seek comments on fixes there. If your fixes involve<br>widespread changes, it gives you a chance to explain why, how, etc.<br>
<br>Next, did you test each release? <br><br></div><div> And next, find someone with commit privileges and a sympathetic ear, and <br>sell them on the patch. Help them, and usually, they will help you.<br><br>Lastly, have patience. It could take months, if not a year or two to get some stuff<br>
coordinated and into a future release. If your mods are seen as possibly disruptive to other<br>parts of the codebase, there may be concerns or reservations that will need<br>to be addressed. If your fix isn't perceived to the be "best" fix for the problem, then<br>
that could hold things up. If your problem is unique to you, it may be passed over for<br>that reason alone. Your patch may even conflict with future plans, or with other<br>similar niche user demands. Sometimes, the patch might be perfectly appropriate<br>
and needed, but would require Digium funds or resources to implement. <br>Such things often stall the acceptance or implementation of patches. Either<br>hang in there if your cause is just, or retreat and cut your losses.<br>
<br>Best of luck<br><br>murf<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Thanks,<br>
<br>
-kkm<br>
<font color="#888888"><br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Steve Murphy<br>ParseTree Corp<br><br>