Thanks Andrew. You are right, and I was wrong. FS project's usage of JIRA is somewhat different than how we use JIRA at work, and thus got confused, as I didn't find the change-management information at the place I was looking. Sorry about the confusion folks.


On Fri, Aug 30, 2013 at 1:58 PM, Andrew Cassidy <andrew@cassidywebservices.co.uk> wrote:

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