Have you guys thought about getting a copy of JIRA or some other bug tracking system?
or fogbugs!
But myself managing large scale development, I know it is impossible any time soon, not likely to ever happen, but we can dream!
We do have these systems internally, but they just aren't something we can make public.
As you may have noticed, Melissa frequently mentions that she has submitted a bug on various crashes or other issues, so we do attempt to track and resolve any reported bugs.
Good point David. I absolutely assume that you're using something to manage bugs.
I think the point here was that these systems allow the development mgmt to make visible bugs of value to people participating in an alpha/beta program.
Where I work we use JIRA as an integral part of the development cycle. We're Agile, so JIRA helps us maintain a product backlog, set priorities, schedule sprints, track velocity, etc.. It also provides a perspective for the customers to see into our world as well as interact with the development process.
Whether JIRA or something else, I think it would be awesome if you provided the same mechanism. It would help people see progress and completion quantitatively and build confidence in the user base.
Food for thought.
I've also noticed that on bugs which get reported via the wiki bug page (which I think doesn't include any Mac Alpha bugs yet at this stage), once a Logos employee (usually either Melissa or Bradley) confirms that the bug is reproducible and is not by design, an internal bug tracking number gets added to the bug (which you can only see if you go into Edit mode). This is a good sign that things won't fall through the cracks, though it doesn't give us any access to internal status info such as what version it is intended to be fixed in. Melissa sometimes posts that info in the forums when it's something that will be fixed soon. Otherwise we can assume they'll deal with it when they get around to it, which might not be for several releases if it's a low priority bug.
