New theme, colours, etc. So why no fix to CWBRN-43213 ???

I can confirm that the color in the rectangles do NOT immediately display a newly-selected color, and that this is a different behavior than prior Sonar releases.
 
When I set a color for a clip, then click on a different parameter in the Clip section of the Inspector Pane for that clip, it DOES then show the newly-selected color.
 
It also displays the newly-selected color if I click on some other track in the Track Pane and then click back on the track/clip that I had previously just changed the color for, so the issue seems to me to simply be that they broke the refresh of the Foreground and Background rectangle colors after you select or change a color.
 
While this appears to be a recent bit of broken, it certainly for ME is not an Earth shattering defect, and by no means does it impact my workflow for any longer than clicking once somewhere else in either the Inspector or Track Pane.
 
Can you please give me a better idea of what the impact to your use of Sonar because of this is?    I am only asking because your post used words like 'staggering' so I would like to better understand its impact on your workflow.
 
As far as the forum search mechanism - it does indeed blow.  Many folks use Google to search for forum threads, and add a couple of Google search filters to tell Google to only search Cakewalk forums for whatever they are searching for.
 
The way to do this is to use: site:forum.cakewalk.com (followed by your specific search terms)
 
Examples:
 
site:forum.cakewalk.com platinum CWBRN-43213
 
or
 
site:forum.cakewalk.com platinum foreground background clip inspector color
 
Try searching like the above, and that should give you good search results limited to the Cakewalk forums.
 
Bob Bone
 

I was a software developer for 38 years, and there has been and always will be a need for companies to balance true maintenance fixes and enhanced functionality, particularly in as competitive a market as recording software.
 
There are zillions of compromises made each and every day, to keep costs down, fix things, and attract new customers.
 
I WILL say that since they have moved to these rolling updates, they have REALLY picked up the pace for getting fixes out the door - though it will ALWAYS be the case that some folks want things done with different priorities, such as more new features, while others want/need fixes to long-standing issues, etc.... everybody has a different set of desires and wishes for what gets fixed or built first for the next release.  A guitar player may have not much use for soft synths, while a classical composer may not have any use for guitar amp modelling, and so on.
 
Further, Cakewalk is a pretty small company, trying to compete and survive, and hopefully grow.
 
In addition, just with regard to fixes, something that IS a showstopper, like Sonar crashes for half the folks trying a new release, will result in Cakewalk working up a hot fix as soon as humanly possible, to fix that for people.
 
Then there are fixes that affect differing numbers of users, and in differing amounts of hassle.  They are CONSTANTLY reviewing the collection of confirmed bugs to see who is likely in the greatest actual need for something to get fixed, versus a small number of folks that use an otherwise little used feature and want something changed.  (I actually seem to fall into that group, as I write prog tunes with mixed meters all the time, and not being able to use an eighth-note in the meter base for the Step Sequencer drives me nuts, but only one or two others have ever complained about that, so it never seems to percolate to the top of the list of what will get fixed).
 
Sooooo - when possible, the forum members do an OUTSTANDING job of figuring out workarounds to as many things where that would help folks out, while waiting for maintenance to come along to fix whatever it is that the workaround is used to circumvent.
 
Cakewalk is also a BRAND NEW way of dealing with support, and there ARE some roll out issues with it thus far.  That will certainly get addressed, and the sooner the better, but that might pull one or more developers and managers off of time that would have been spent either fixing bugs or building new stuff.
 
After using Cakewalk products for well over 20-25 years, since the days of DOS and Twelve Tone Systems, I CAN tell you that the folks working there are ALL passionate about doing what they can to keep things improving in as many areas as they can - maintenance, features, 3rd-party agreements, support, sales, and the forums, etc.
 
I agreed to try to help out, as did a bunch of others, to act as forum hosts to free up some of their resources to be able to get more fixes and development done, by us helping with some of the routine admin kinds of forum things, and am happy to be doing so, because it helps (I hope).  
 
In addition, the folks in these forums - regular users - are a HUGE pool of knowledge to draw from for all kinds of assistance, figuring out why Sonar may crash on one guy's computer when t doesn't for the majority of folks, or how to do clean installs, or moving things around, or a thousand other things.  I have seen forum members repeatedly bend over backwards trying to help each other out.  I am SO proud of the forum folks for the level of time and effort they are willing to invest in helping others out.  It is AMAZING.
 
We are a MESS, but we ARE family.  A giant bunch of folks trying to use Sonar to express ourselves through music, and that is a really really cool thing, as I see it.
 
Bob Bone
 

Skyline_UK
It's not a work showstopper for me, of course.  I guess I'm just old fashioned and bemoaning a couple of principles here.
(1) In my book it's simply inept to introduce new bugs and those should be sorted asap, especially as it's been laid out on a plate in a CWBRN.  (2) It's poor customer service to have a bug report system, to enable users to help the company hone its product, and then fail to have a simple system whereby someone reviews them/updates them until closed off. Other music software companies I deal with operate such 'ticket' systems very efficiently.
(BTW, thanks robert_e_bone and maximumpower). 

As others have said we have many issues in our system and they get prioritized and handled as and when resources are available. I think we've done a fairly good job of demonstrating that we are taking our backlog seriously and address issues pretty much every month. Regarding (1) in the real world its not that unusual for regressions to occur and it has nothing to do with ineptitude :) The permutations in modern software are staggering and often engineering, QA or customers won't notice a problem for weeks or months.
 
Your specific issue somehow slipped through the cracks and I'm sorry about that. Problem reports are typically triaged by customer support first, before they make it into the engineering queue since there are tons of duplicates or issues that have insufficient info that sometimes requires follow up with this customer. This wasn't the case for your issue however. I've transitioned it to the engineering queue and it should get investigated.