I agree with TM. (I regularly read his posts on Gearslutz and he is a very reasonable person.) I was astounded that a log of bug fixes wasn't released with the new subscription and "Sonar 2015".  It should have been front and center, or at least a partial log with more to follow. Just good business and marketing sense. There is a lot of competition for consumer dollars at the moment and Cakewalk needs to be impressing at every opportunity. However, that's not to take away from Cake's obvious hard work. But to me that was a big oversight.
 

it's simply not a good sign that there is still no bug fix list. it makes it seem like it's not all that impressive and that they're holding it back on purpose so that more people take the gamble and upgrade.

This is not "a bad sign" or anything like that.
 
Anyone who's been with SONAR through the last few releases knows that the bug list is never released at the same time, or even shortly after, a new release. 
 
However, we do eventually get it; and what's more: along with it we tend to get a serious of in-depth, technical blog posts on various topics about the new release, which are, in my opinion, solid gold.
 
So I'll take the Cakewalk way of doing things, thank you very much.
 
If you have concerns, then don't buy the product until the bugfix list is posted.

Spencer
they're holding it back on purpose so that more people take the gamble and upgrade.

No. They would not do that. I just think the importance of the announcement of a log of bug fixes got lost in the process or whatever. The most common criticism of Cake and Sonar in the general audio community has been the response to bug fixes. Because I have always used Pro Audio/Sonar, I have an "emotional" attachment to see Cakewalk succeed. I have bought Platinum but I am yet to install it.

stickman393
This is not "a bad sign" or anything like that.
 
Anyone who's been with SONAR through the last few releases knows that the bug list is never released at the same time, or even shortly after, a new release. 
 
However, we do eventually get it; and what's more: along with it we tend to get a serious of in-depth, technical blog posts on various topics about the new release, which are, in my opinion, solid gold.
 
So I'll take the Cakewalk way of doing things, thank you very much.
 
If you have concerns, then don't buy the product until the bugfix list is posted.

This is hasn't been my experience at all. At least with the subsequent updates, you'd go to the support page of the Sonar product and with the download link there is an extensive list of supposed bug fixes. But aside from that, if ant any point the bug list was not released with the software, that doesn't make it right. Even if it was a fact that they never release bug fix lists with the software, why does that make it okay? 
 
When folks are doing serious work with Sonar, in general, and perhaps looking for a bug fix, how do you brush them off by saying "don't buy it until the bugfix list posted"? Why does every effort go into quashing the reasonable & naturally, expected bug fix list with ridiculous rationalizations of why it's not being released??
 
Repeat: there is absolutely no excuse for the list not having been published by now. NONE.

the comments from the bakers in this thread make it seem like an afterthought, to publish a change/fix list, when really it should be an asset of the release

rtucker55
I'm very disappointed that the below did not get fixed. I waited 10 months for this and it is a big deal for me. If I would have known it was still an issue I would not have purchased. I would like to know why and if it ever will/can be fixed.

CWBRN-23924 Report Details

ProductSONAR ProducerVersionX3StatusStatus ChangedSummaryShow/Hide Track state in PRV Track Pane does not persistRepro Steps

1. In a project with multiple MIDI tracks, display them all in the PRV's Track Pane
2. Click the "Show/Hide Track" on several of them
3. Save the project, close it and re-open it.

Expected ResultsThe PRV's Track Pane will show or hide the same tracks that were displayed or hidden when the project was saved.Actual ResultsAll tracks are shown in the PRV, none are hidden.Audio Device- - Integrated /On-board Audio - - -OSWindows 7 64-bitReproducibilityReproducibleFiled2/5/2014Last update
2/5/2014

This sounds like a classic case of trying to implement display changes to a locked screenset.


 
Are you sure this isn't the case here?

was the bug confirmed?

Not likely as I don't use screensets. (knowingly)  As I stated the Cake support guy also duplicated the issue, on a New project, while we were on the phone.
 
Give it a shot, create a New project insert 3 midi blank midi tracks, Open the PRV, Pick the 3 midi tracks so they show in the PRV's track pane. Click the HIDE button for one of the tracks, save the project and close it. Open the project and all 3 will be showing vs. 2 showing 1 hidden, as expected.

pwalpwal
was the bug confirmed?

Hi pwalpwal,
 
See post #7 for Seth's reply. I'm not sure how to interpret the reply other than they know it is an issue but is not really being pursued. Perhaps not enough of an issue to pursue.