Dear All, Just a suggestion - how hard would it be to have your bug track system send devinfo a daily or weekly digest of every new bug with 5.6 in the subject line. That way we could keep a track on what is causing you guys problems and what isn't. We might even be able to help! At least it would stop this endless spam on devinfo ;-) All the best, Julian Luton
-----Original Message----- From: Les Mikesell [mailto:[EMAIL PROTECTED]] Sent: 13 August 2002 05:32 To: Charlie Brady; Greg J. Zartman Cc: Devinfo Subject: Re: [e-smith-devinfo] Reporting bugs (was Re: bug posting? [was [5.6] unable to login to) >From: "Charlie Brady" <[EMAIL PROTECTED]> > > > However, it seems to make good sense to cc devinfo with bug reports, > > especially on something that is alpha. > > On no account cc devinfo. If you do that, every followup on devinfo > will > open a new ticket in our bug tracking system (as we've said here before). > This wastes even more of our time. How do all the other beta testers avoid wasting their time dealing with the same bug if they aren't discussed publicly? I thought the point of open source development was to share this sort of thing. Les Mikesell [EMAIL PROTECTED] -- 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 -- 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
