CakeAlexS
It's impossible to discuss 40+ issues on one thread with multiple stakeholders, sorry total nightmare, how could you keep track of it all?
 
Did you check the link on post #2, that is the main thread (well it's building up to be). This is a single post linking to all the issues (an index if you like).
 
Thanks...

Alex makes a good point here. I also know a thing or two about long threads. Its a massive undertaking to keep everything up to date.
 
That doesn't prevent one from being annoyed by a bunch of threads from the same person. Though they are important and very much needed.
 
Its a bit easy to criticize when we don't look at all the angles. One thing for sure is this forum is about information and both Alex and Jlien are doing us all a big favor in providing a lot of it.   

Having seen threads posted both ways, all in one and separate for each issue, I ABSOLUTELY prefer each issue to be in its own thread.
 
It is WAY easier to debug, and for folks searching for solutions, it is much easier to have them separate.
 
Bob Bone

I must admit, when i first logged on an hour or so ago, my immediate thought was "what on earth are all these posts by Alex"
 
But skimming through the titles immediately confirmed what they are, and my thought became "nice one Alex - you're putting in a lot of work here for everyone's benefit and he definitely deserves a round of applause. 

Just FYI - once something is entered into the system, Cakewalk tracks it from there. It's not really necessary to use the forum to track things...the main value I've seen for the forum with respect to bugs is people a) finding issues, b) posting steps to reproduce as a "reality check" to make sure it's not some system-specific glitch, and c) if a bug is confirmed, reporting it to Cakewalk.
 
This is basically what made it possible for CW to exterminate so many of the remaining bugs, especially because quite a few of them were either fairly trivial or relatively rare. Finding these usually requires a zillion users banging on the software, and that's exactly what happened.
 
It's all good   I just want to make sure that the forum doesn't have extraneous information that crowds out other information that may have higher value to the community as a whole.

The obvious solution would be to have a bug reporting sub-forum.

Bristol_Jonesey
The obvious solution would be to have a bug reporting sub-forum.

This!

joden

Bristol_Jonesey
The obvious solution would be to have a bug reporting sub-forum.

This!

Yup.

+1... plus a layout designed for said purpose, like "traditional" bug reporting tools are.

+1

+1 :-)