Steve Hanselman
2004-Aug-25 00:01 UTC
[Asterisk-Users] Closing bug reports without fixing the repor ted problem
[vested interest: I reported that bug!] I agree with this, a system that has x bugs still has x bugs even if you close them, I think they should be closed by houskeeping if they can't be reproduced and the person that reported them can't provide a way to replicate, but they shouldn't be closed because nobody has fixed them for a while. This seems to be the case on a number of entries. Steve -----Original Message----- From: Rob Wise To: asterisk-users@lists.digium.com Sent: 25/08/04 07:01 Subject: [Asterisk-Users] Closing bug reports without fixing the reported problem While this is more a question for the bug system admins, it does impact on the whole Asterisk community so I'm going to ask it here. Why does it seem to be normal procedure to close bug reports which have not been resolved? Twice now bug 1915 has been closed off without a solution being found, much to the protest of those who are suffering from the reported problem. I am curious to know why this is being done as it does not seem beneficial in any way to the Asterisk project to hide problems by closing the ticket rather than leaving them open so they can be worked on. I also am curious to know what other members of the community think of this. Rob Disclaimer: I am one of those affected by the bug, and it is still present in today's CVS head. _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users The information contained in this email is intended for the personal and confidential use of the addressee only. It may also be privileged information. If you are not the intended recipient then you are hereby notified that you have received this document in error and that any review, distribution or copying of this document is strictly prohibited. If you have received this communication in error, please notify Brendata immediately on: +44 (0)1268 466100, or email 'technical@brendata.co.uk' Brendata (UK) Ltd Nevendon Hall, Nevendon Road, Basildon, Essex. SS13 1BX UK Registered Office as above. Registered in England No. 2764339 See our current vacancies at www.brendata.co.uk
Peter Svensson
2004-Aug-25 00:17 UTC
[Asterisk-Users] Closing bug reports without fixing the repor ted problem
On Wed, 25 Aug 2004, Steve Hanselman wrote:> I agree with this, a system that has x bugs still has x bugs even if you > close them, I think they should be closed by houskeeping if they can't be > reproduced and the person that reported them can't provide a way to > replicate, but they shouldn't be closed because nobody has fixed them for a > while. > > This seems to be the case on a number of entries.Perhaps the trigger-happiness is related to the upcoming 1.0 release? If this is the case (pure speculation) perhaps a new state "closed pending 1.0" for bugs that will not be addressed until after 1.0 can be added? Peter
Seemingly Similar Threads
- recursibve listing of file owner, possible?
- asterisk no longer compiles on gcc 2.95
- Providing Telewest in the UK with per extension outbound callerID
- Temporarily placing confbridge participants on hold - two way muting
- Transfers on PRI connected channel banks and legacy PBX's