> that first email, my god, that should be titanium-and-gold-plated standard of a bug report.
It's a thing of beauty. It even includes versions of software used!
My daily experience with bug reports are that they 50/50 won't even include a description, just a title. It's such a cliche already, but "project name is broken" makes my blood boil. What environment? What were you doing? Is this production? How do I test this bug? (from an Ops perspective) When did you notice this? Has anything changed recently to possibly cause an error?
It's a thing of beauty. It even includes versions of software used!
My daily experience with bug reports are that they 50/50 won't even include a description, just a title. It's such a cliche already, but "project name is broken" makes my blood boil. What environment? What were you doing? Is this production? How do I test this bug? (from an Ops perspective) When did you notice this? Has anything changed recently to possibly cause an error?
Arg, my blood pressure!
/offtopic, sorry.