>
>Thanks for the feedback, Ira. It makes me very sad to hear what you say and I
>hope that we can get more resources from the community to assist in the
>process to make it more friendly. We want to get those bug reports. The one
>thing I hate to hear when I'm travelling at conferences is that "oh, I known
>that bug for a long time but did not bother to report it."
>
>Apologies for your experience with the bug process.
>

Indeed, it seems as though there might be a problem of discoverability of how 
to report issues.

Is it too burdensome to suggest attaching this link (along with a short 
description) to the footer of list e-mails?

http://www.asterisk.org/developers/bug-guidelines

That does a fair job (though not perfect, and I think suggestions for 
improvement are welcome) of detailing the process.  It's probably also 
incumbent upon us all, as a community, to do a better job than just "report it 
on Mantis".  I'm quite certain every one of us would like the most stable, 
bug-free code in Asterisk as is possible, and if it takes an extra minute or 
two of our time to help get the issues reported in the first place it will be 
time well-spent.

- Brad

The contents of this e-mail are intended for the named addressee only. It 
contains information that may be confidential. Unless you are the named 
addressee or an authorized designee, you may not copy or use it, or disclose it 
to anyone else. If you received it in error please notify us immediately and 
then destroy it.


--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
               http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to