ReEasier bug reporting (demo)

[Brent_Easton]

Michael,

How do the rest of us find them? Or would you just post them here?

They appear automatically as new Sourceforge Bug Tracker items (sourceforge.net/tracker/?group_ … tid=594231)

B.

• M.

On 28/05/2008, Rodney Kinney rodneykinney@comcast.net wrote:

Cool idea! So that’s where all those mysterious bug reports I’ve been
getting from SourceForge came from.

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

[Brent_Easton]

What do you see as benefit of having them be submitted by a special user?

None, on reflection

In the interests of keeping complexity for the user down and making it
easier for us to spot untended-to bugs, I thought it would be best not
to ask the user for a title. There’s a good chance that that user won’t
come up with good title anyway.

Yes, Agree.

Any guess on how many of these we will get?

One? Hundreds? Millions? No idea. Hopefully we’ll get exactly one for
each bug.

Unlikely. We will probably get one from each user for each bug.

I’d considered doing the reporting by email, but wasn’t sure where it
should be sent. I guess I could create a ‘vassalengine-bugs’ list which
would receive these instead. I don’t see that it would affect the volume
of reports either way. One advantage of doing it by mail would be that we
could cc the bug’s reporter when the report goes out to the list, though.
(There’s also the fact that it was a PITA figuring out how to POST the
data to SF, and I’d hate to toss it out, but if we think email would work
better for this, I’ll go ahead and kill my darling.

I like both options.

The submit to sourceforge is perfect for the general public to send in bugs reports. They don’t really know who it is going to or to where, but they are happy to submit them.

The submit via email option I see useful where you are working closely with a tester trying to sort out a bug. You might be generating svn versions for testing and the same/similiar bug is occuring over and over again. Rather than submitting the logs to sourceforge, your tester can use the email option to send them straight to you.

B.

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

[uckelman]

Thus spake “Brent Easton”:

Any guess on how many of these we will get?

One? Hundreds? Millions? No idea. Hopefully we’ll get exactly one for
each bug.

Unlikely. We will probably get one from each user for each bug.

Yes, I agree that it will lead to duplicates. I’m not sure how bad
that is, though. If it’s an uncaught exception that’s hitting a ton
of people, then it’s something we’d want to fix right away anyhow.

I’d considered doing the reporting by email, but wasn’t sure where it
should be sent. I guess I could create a ‘vassalengine-bugs’ list which
would receive these instead. I don’t see that it would affect the volume
of reports either way. One advantage of doing it by mail would be that we
could cc the bug’s reporter when the report goes out to the list, though.
(There’s also the fact that it was a PITA figuring out how to POST the
data to SF, and I’d hate to toss it out, but if we think email would work
better for this, I’ll go ahead and kill my darling.

I like both options.

The submit to sourceforge is perfect for the general public to send in bugs r
eports. They don’t really know who it is going to or to where, but they are h
appy to submit them.

The submit via email option I see useful where you are working closely with a
tester trying to sort out a bug. You might be generating svn versions for te
sting and the same/similiar bug is occuring over and over again. Rather than
submitting the logs to sourceforge, your tester can use the email option to s
end them straight to you.

So you want a checkbox and a field for a recipient email address?

–
J.

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

[Brent_Easton]

So you want a checkbox and a field for a recipient email address?

Yes.

Or a dropdown with 2 options

Send report to Vassal Developers (default)
Send report to Email Address

The first sends it to sourceforge, the second asks for an email address.

B.

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

[Tim_M]

It might also be useful (unless you can tell already) to have 3 checkboxes
in the report that helps you zero in how the bug is occurring (for
duplication / testing).

These would be:

Playing module
Editing Module
Managing/launching module

Have one of these checkboxes required in the report to help filter types of
problems, as the optional ‘what were you doing’ part is sure to have as many
varied responses for the same bug as there are users reporting them and
modules in which they were happening

Post generated using Mail2Forum (mail2forum.com)

[Brent_Easton]

Tim,

It might also be useful (unless you can tell already) to have 3 checkboxes
in the report that helps you zero in how the bug is occurring (for
duplication / testing).

These would be:

Playing module
Editing Module
Managing/launching module

Have one of these checkboxes required in the report to help filter types of
problems, as the optional ‘what were you doing’ part is sure to have as
many
varied responses for the same bug as there are users reporting them and
modules in which they were happening

I don’t think this is really needed - This info is included in the log file

B.

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)