I may be wrong, but this is my understanding: In a way it is a timeout, but usually where they dev has been waiting for a response from the reporter to say whether or not the fix worked. So, in most cases, it's been fixed but the fix has not been verified by the reporter. On 30 August 2013 09:16, Jayanth Acharya <jayachar88@gmail.com> wrote:
Was browsing through the JIRA database, trying to identify any discussion regarding the audio distortion, and I found several tickets that have been closed (at least, that is how I interpret the closure), because they have been inactive for some time (15 days??). Which effectively means that the bug-closure is not by solving/fixing, but simply timing-out, in the hope that the bug "somehow magically" got fixed in the latest release ?? I hope I am terribly mistaken in my interpretation.
J
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- *Andrew Cassidy BSc (Hons) MBCS SSCA* Managing Director *T <info@cassidywebservices.co.uk> *03300 100 960 *F<info@cassidywebservices.co.uk> *03300 100 961 *E <info@cassidywebservices.co.uk> *andrew@cassidywebservices.co.uk *W <info@cassidywebservices.co.uk> *www.cassidywebservices.co.uk