[asterisk-dev] Bugs/patches 16033 and 16590 ignored forever

[Leif Madsen]

I'm sorry you're frustrated. Unfortunately with the amount of resources we have 
to move issues forward, these particular issues have not made it onto any 
developers plate at the moment.

As you may have noticed, there are over 600 open issues in the Asterisk project 
alone, so we're doing our best to keep up with all the issues filed. I'm 
estimating there are about 5-8 issues filed a day with a mix of minor issues, 
crash issues, feature submissions, and non-issues (configuration problem on the 
part of the reporter).

These issues will get a review and moved forward as soon as time and available 
resources allow.

Thanks for your understanding.

Leif Madsen - Asterisk Bug Marshal

Kirill 'Big K' Katsnelson wrote:
> I keep bring these up to the attention of the list to no avail for 
> months! This is the last time I am bothered. There are two very real 
> very creepy bugs in asterisk that I submitted patches for, and the 
> patches are sitting there "ready for testing" month after month. Every 
> time I post a message here about these patches I am getting responses 
> like "thanks for reminding us," "how nice you are being persistent," 
> and... that ends the attention span.
> 
> If anybody is interested, the patches are:
> 
> https://issues.asterisk.org/view.php?id=16033
> [patch] Autocreated peers not deleted when unregister explicitly, become 
> zombies
> 2009-10-08 07:06 lmadsen Status acknowledged => ready for testing
> 
> https://issues.asterisk.org/view.php?id=16590
> [patch] Monitor resumes recording after SIP transfer despite 
> StopMonitor() having been called
> 2010-01-13 09:19 lmadsen Status new => ready for testing
> 
> I am dropping these off my monitoring list. If they are gone, they are 
> gone. I will continue to maintain them privately for myself.