On 08/11/2005, at 5.55, Paul Bissex wrote:
What's the official procedure for filing bug reports? There's this mailing list, bugs@macromates.com, the various areas of the wiki, the FogBugz site... what's the best way to deliver bug reports without driving Allan to distraction?
My preference depends a bit on the type of bug report, of course this is not possible for the person reporting the problem to know, but here are some hints:
=> this list: if it's a problem likely introduced in a recent build or affecting a lot of people. I.e. stuff that potentially could lead to a lot of duplicate reports.
Bugs where the reporter is unsure if it's really a bug, by- design, or maybe something else interfering, should preferably also go to the list (since others may be able to answer it, and save me some time).
Everything related to bundle items should also go to the list, since a lot of the stuff is done by other TM users (who for the most part are subscribed to this list).
=> bugs (at) macromates: if it's crashing or acting in some way that it really shouldn't (e.g. refuses to open some document). Logic being that this is probably a case where I need more info, and little is (probably) gained from reporting this in public.
=> fogbugz: for everything else :) that is, stuff that's not affecting stability, and not a real problem for using the application.
In principle I would like to use FogBugz for everything, but it has two drawbacks:
1) users can't search the database, hence this list is better for what's likely to become a duplicate
2) one has to manually click “subscribe” to be notified about changes to the ticket, which no-one does, hence email is better (for the reporter) when I'm likely going to request more info (there are several open tickets in the database with status “waiting for more info”)
Hope it helped clarify it a little.