stevec
I guess what I'm really saying is that the company I work for would never have a build signed off and ready for release, only to hold back from uploading it to the public because a fixed list was not yet complete. I know that from the outside it's all the same because the user-base doesn't know the difference either way, but when you have users waiting for fixes and enhancements, something has to take priority. And shiny usually wins. 
I've never had to compile one of these lists myself but I know what goes into them and it can be a PITA. You have to separate externally vs. internally reported issues, those reported against a commercial release vs. those reported against internal-only builds, and check the wording of each defect to make sure it's clear since it's released publicly. And then double-check your work. Sure, each step may not be overwhelming, but everyone has some existing role within the company and simply finding time to do all that can also be an issue... Anyhow, just my additional $.03.
@ Bob... "OT: are you the one with the Nebula and CPU discrepancy vs. Reaper? I can confirm that as well". No, that wasn't me. I think I may have read something about that at some point but I don't really use either product... though I do find both to be interesting...
Hmm, I probably saw a thread with the name Steve or something then. Alrighty then, thanks. P.s. they are indeed interesting!
But yea like I was saying, even against the backdrop of the idea that creating those lists are difficult, if one believes it or not, it always comes back to the fact that it could've been work delegated amongst the development of the software to ensure its timely release. It's like, say, leaving a feature out and justifying it with "it's a lot of work and takes times but we'll get on that later." Naturally it should've been worked on as part of the development. "Finding the time" should all be contained within the release schedule for any constituent of a release. Simply, if any part of it is incomplete, then it is not done.
So if one comes back with "the actual software release is priority because users are waiting for fixes," don't you think it is worse for business no less if those said users, in anticipation for fixes, realize that after spending money on the upgrade find out the issues have not been fixed! And doubly worse, perhaps have more bugs on top of it.
Vastman
SteveC... you are very eloquent!
Alex... I luv ur humor! Helps us suffer through Jerks...
TM...Dude... I rarely go there, but you're a jerk.
Don't buy the friggin' software till you see the list
Quit spewin' ur friggin' venom
The force that's within you is ugly...
Your insinuations are putrid
get a life!
Oh, yes, and I'll reitterate... if it's sooooo friggin' important to you to see the list, wait for it and if it meets your approval, upgrade.
What a waste of forum space...
Dana the problem with not thinking for yourself, as you are clearly afflicted with, is you in particular add nothing to conversation or debate. You call what I am naturally inquiring about, as a long supporter of Sonar/Cakewalk, venom? You barge into a thread and say absolutely nothing: you could've literally came in here and typed "asjhajksahsjhasahereuajdbjj454raed" and it would've been the same, save for the fact you wouldn't be unnecessarily insulting my inquiry. Somebody questions something legitimate, while others pondering the same, and they are a jerk! A jerk says to a long-time, loyal customer: "don't friggin buy it until the list is released." Get what I mean jerk? Legitimate inquiry and concern met with childish, useless banter. But my posts are putrid? You get a clue.
So, just like Alex, as useless as he is to my posts, consider yourself blocked :)
This way I don't have to address your, I am sure, follow up non-sense. You want to act like a child, you'll be treated like one.