As it is now thanks. Can't lock Cakewlak into how monthly releases go. The next feature may depend on certain bug fixes etc. too many variables. Leave it alone and let Cakewalk do their thing as it needs. Maybe one month we won't even get a release because there just hasn't been enough time. Maybe only some content that month.

Cakewalk have already stated the current method will get out regression fixes quickly. If they don't get out a release in a month that would screw with their monthly subscription plan. The big question is delivery.

I'm good with the monthly release schedule too, as it is.  I wouldn't want to update more often than that, but I also like that new toys are introduced monthly.  I like the balance between the two.
 
My hope that that as the process continues and development (and testing) adjusts, more obvious bugs like this Control Bar issue become rare occurrences at best.   And that subsequently, discussions like this would just never need to happen in the first place.   Well, that's my ideal SPlatWorld.  
 

In my "Splatworld" (copyright stevec), if they break it, they should fix it.
There should be a quick fix for major issues such as this.
It's a newish feature that's been added, and we shouldn't have to wait a month for a fix.
I know it will be addressed in time, I've grown to have confidence in the baker people, but the Control Bar is central to the workflow of everything . . . and having to modify it every time I start up Sonar is most annoying, time wasted.
Hopefully, they'll come up with something marvelous, next upgrade, such as a way to save your Control Bar preferences, when it does get fixed.

The majority of the early reporters on this particular problem, myself included, graded this problem as an 'annoyance', but not a big deal.  I'm not saying it isn't a major problem for you, but for most it wasn't presented as major.  This *might* have something to with a fix for it coming more slowly than a quick turn-around hot fix.
 
Overall my assessment is that these guys have their hands fuller than they have ever been, and they have more pressure than they have ever had before to make things right.  Now we have to wait and see how they handle it.
 

noynekker
In my "Splatworld" (copyright stevec), if they break it, they should fix it.
There should be a quick fix for major issues such as this.
It's a newish feature that's been added, and we shouldn't have to wait a month for a fix.

Actually you're not waiting a month for a fix, you're waiting a month for the fix and the testing to make sure there isn't some other issue in there that's going to cause another problem. In a case like this where there's a bug caused by fixing a different issue, I think it's very important that Cakewalk do thorough testing before doing another release. If I was Cakewalk, once I released this control bar fix I wouldn't want to have to do another control bar fix somewhere down the road because it wasn't tested adequately.
 
That said, if Ben said they were working on a fix ASAP, I would take that to mean in the next release.

mudgel
The next feature may depend on certain bug fixes etc. too many variables. Leave it alone and let Cakewalk do their thing as it needs. Maybe one month we won't even get a release because there just hasn't been enough time. Maybe only some content that month.

There will definitely be different mixes of features and content with each release. One of the benefits of making content a significant part of the membership program, aside from most people digging it, is that it's independent of the program itself. So if the Bakers are working on some big feature that monopolizes their time, we can include more content. OTOH when there are a lot of features, that gives the slack to create more complex content.
 
I assume having fixes will be a consistent feature of each release, but the number will vary. 

Anderton
...that gives the slack to create more complex content.
 

Hmmm...  anything particular in mind?  
 

Anderton
Actually you're not waiting a month for a fix, you're waiting a month for the fix and the testing to make sure there isn't some other issue in there that's going to cause another problem. In a case like this where there's a bug caused by fixing a different issue, I think it's very important that Cakewalk do thorough testing before doing another release. If I was Cakewalk, once I released this control bar fix I wouldn't want to have to do another control bar fix somewhere down the road because it wasn't tested adequately.

 
Another reason for #13/#15/#17. A whole month for testing regression bugs.

Doktor Avalanche
Another reason for #13/#15/#17. A whole month for testing regression bugs.

If Cakewalk had the manpower to do that, they wouldn't rely on us.