> Sending a separate bug report to devinfo provides the following: > > - potential for feedback from devinfo members to confirm/deny the bug > - potential for devinfo members to post back the fix > - sharing of bug reports on devinfo for general knowledge > I think it is vital to share these reports. I think you simply have to > state that the correct process is to author two complete separate >messages.
I completely agree with Darrell's statement. I would further elaborate with an example. Lets say that someone reports a bug to Mitel that for one reason or another gets tagged as a low priority item (i.e., not a big issue, but slated to be fixed before the next release). "Echoing" this message to DevInfo may attract someone to jump on the issue and produce a draft fix. Regards, -- Greg J. Zartman, P.E. Vice-President Logging Engineering International, Inc. 1243 West 7th Avenue Eugene, Oregon 97402 541-683-8383 fax 541-683-8144 -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
