I need insight into user, power user, and dev bug reporting

by **Braids** » 24 Jul 2011, 01:40

i updated the README.txt regarding bug reporting.

i've been assuming that beta testers should report bugs to the beta topic corresponding to their version. i've been assuming that everyone else (power users and developers) should use Mantis directly.

is this correct? what methods do we want various people to use to report bugs? should i include more of Underflow’s “How to File a Bug Report via Google Code”?

commit specifics are at https://www.gitorious.org/cardforge/cardforge/commit/1f94f841410d1c8d810ee3bec51be6e397aa4b84

by **Jaedayr** » 24 Jul 2011, 01:56

Good question. I just reported a new bug on Mantis but am not sure how to indicate exactly what rev of Forge I was testing with.

by **Braids** » 24 Jul 2011, 02:26

Jaedayr wrote:Good question. I just reported a new bug on Mantis but am not sure how to indicate exactly what rev of Forge I was testing with.

part of the problem is it's not a freeform field.

if it were, i would use the 7-character hexadecimal identifiers as found in https://www.gitorious.org/cardforge/cardforge/commits/master

for now, just place the hex identifier in the summary or description.

i applied for Mantis admin status; we'll see when Rob approves.

by **Snacko** » 24 Jul 2011, 08:40

The full identifier is 40 character long, however first 7 characters should always be unique enough to pinpoint the actual revision.

by **Braids** » 24 Jul 2011, 15:56

Braids wrote:
Jaedayr wrote:Good question. I just reported a new bug on Mantis but am not sure how to indicate exactly what rev of Forge I was testing with.

`
there are now new fields, {Git Rev Detected (hex)} and {Git Rev Pushed (hex)}. they only accept 7-digit lowercase hexadecimal. the former is optional; the latter is required in order to mark an issue as resolved.

if this is too draconian, please let me know. if course, you could always enter 0000000 in the latter field if a git change weren't necessary.