Some MORE random SE:V questions

[Fyron]

Aaron's the one to convince, not us. Aaron has never been particularly good at community relations. Posting his lists online might work, but I fear he would only keep it up to date for so long before letting it wallow in the realm of un-updated web content.

For reference, he turned down the idea of making primary use of the bug/issue tracker on SE5.com due to it being "too late in the process" to change gears.

[capnq]

Also, the number of different people reporting the same bug factors into how much priority fixing that bug gets.

[Q]

capnq said:
Also, the number of different people reporting the same bug factors into how much priority fixing that bug gets.

Sorry but here I have to disagree completely.
There hard to find bugs, that will therefore be only reported late and from one person and yet this may be a game killing bug if it happens.

[Slick]

Yes, that's the problem. Knee jerking on emails shows no organization.

I still can't see why the beta testers don't maintain such a thing for him.

[Captain Kwok]

It's not quite as described.

MM maintains a list of reported bugs. Factors considered are reproducibility, save-game, severity, frequency, etc. Earlier in the beta, Tampa_Gamer maintained an extensive list of bugs/issues.

E-mail frequency (popularity) is associated more with getting a requested feature or change added sooner rather than later.

[Slick]

"getting a requested feature or change added sooner rather than later" seems to me like knee jerking to emails. It does not seem like a systematic approach to fixing bugs in order of severity and, possibly, adding feature requests if practical as desired.

[Fyron]

If you ignore the ranked listing of bugs by severity et all that Kwok mentioned, then certainly. Bugs are treated differently than feature requests; you don't need a ton of emails about a bug to get it fixed. Aaron does have organization, he just doesn't make it public.