That's pretty neat, but what about the new forum - is there a special place in the works for bug reports in the forum? Many forums have this, and it would nice since reports wouldn't get buried by email, you could click on "Bug Reports" in the respective software group or something and there they would be, you wouldn't have to search through the mailing list. Another advantage of this is users can avoid duplication by quickly seeing if they should file a bug or not by looking in "Bug Reports" in the forum.
My 2c. Since many "bug reports" end up being misunderstandings or launching points for discussions for other ways to approach a problem, segregrating them from the main discussion would likely be less valuable for the community at large, although it might make our work a little easier. My suspicion is that most people wouldn't read that forum and the people reporting the bugs would either cross-post (blah), or never benefit from the collective wisdom of the main lists.
The contents of the bug tracking system will never be made fully or even partially public, apart from the personal email responses one might get from support@.
The reason for this is that in most cases where we find a "real" bug, the internal discussion of its resolution may be speculative, in terms of the technology of unannounced future releases, or in a multitude of other different ways entirely not the sort of thing we would wish to be generally broadcast about.
If you have submitted a bug report to support@ and not received a satisfactory response, please feel free to email me directly and I shall chase it down for you.
I can tell you about some Max bugs I passed to Cycling that took 6-8 months to fix – with me constantly sending them reminders. There is still an outstanding bug I spent many hours on pinpointing that is waiting for a solution. So please don’t tell me that everything is rosy in the bug squishing department.
But my point is not how quickly or slowly bugs are fixed. My point is that if I had to spend hours to figure out that my program isn’t working the way it should because of a buggy object AND Cycling confirmed this bug YOU should be able to read about it in a “known issues/bugs” database so you won’t need to step into the same trap. This is not about how fast the bug is fixed but how transparent it is made to other users once it has been revealed.