What sort of techniques or procedures do you recommend for those of us that want to hunt and report bugs to CIG? How can we most efficiently go about collecting the information that you need?asked by Amontillado
TL;DRGood bug reports are concise and clear, with steps and as much information as possible, including what you did beforehand, so QA can write good repro steps; adding a release-notes focus request is only an idea.
So this is kind of a question for you ...
Yeah, I believe this is probably a QA question and Issue Council type question. So basically what we primarily want is people to be concise, clear, clear steps running through things you started doing but also include ... sometimes you're only reporting the thing that you saw and what you were doing when you saw it, but sometimes what you were doing before that impact things.Like we had certain situations where people were getting disconnected while joining Crusader they would just tell us "hey, I got disconnected when joining Crusader" but, you know what, it was because they were joining Arena Commander before they transitioned to Crusader and their tokens weren't getting cleared and that was the issue.So as much information as possible they can provide is usually the best for us because then we can pick through all that information and get really good steps for the developer so they can actually get a fix in.
So I know with like release notes and stuff we have ... do you guys set the release notes?
Yeah.
So maybe in there we can be like "hey guys, can you focus on this?" Do we do that right now?
We don't do that right now. That's not actually a bad idea. You know if somebody was a Producer ...
What?
... they might be able to push something like that forward! That might be a good idea going forward.
Man, see this is what happens when I open my mouth!
Yeah. Exactly!