I am a big fan of the new rolling update model and have at least tried the early release candidate every month with the exception of 2017-02. I also believe Sonar to be at its peak, faster and more stable than any time in the 25+ years I have been using Cakewalk products . That said, with the official release running a bit late, I have realised how good it is to have a stable DAW without any uncertainty of a new update causing issues (I have run into a few show stoppers sInce the new model was released). I wonder whether the solution doesn't lie somewhere between the new and old models - maybe updates every two or three months? Obviously I can choose to do that now, but I can't help but think that Cakewalk must feel the pressure of a monthly release date that could perhaps be at the root of the occasional isues we have seen slipping through the cracks. Again, I understand you can always roll back, but I am not convinced that these  problems don't unduly damage Cakewalk's reputation to the wider DAW community.
 
I am not for one second denegrating all of the hard work the bakers do - I think they are brilliant. I just wonder whether the monthly major releases have created an unnecessary rod for their backs. I for one am more than happy to give them a bit more time!
 
Just wondered what others thought.
 
Peace:)

I think if anything people should be less eager to jump on the newest bleeding-edge updates if they are worried at all about stability. I personally don't run a studio and it's not the worst thing ever to me if there are some hangups with an update. I also think the February update is indicative that Cakewalk is willing to hold back if they aren't feeling completely ready for a final release.

I guess its a double edged sword.
some that update and have issues would have to wait another 3-4 months for a fix.
I myself have been very pleased with the monthly updates. I cant honestly say I have yet to rollback because of a version that was less than satisfactory. Im know some have needed to because of keyboard shortcuts, synth rack personal preferences. exc. But I have been pleased with the monthly updates and hope they continue the way they are. this is only my opinion though. im sure others will agree, disagree.
 
EDIT: I respect your opinion though..and your idea of why. I also agree with you in many ways.
I just like the way the monthly updates remedy issues (that we used to wait months to be fixed).

I like the monthly update model. I think the scheduled approach 'keeps the train running'. As this month demonstrates, the early release offers a feedback loop for updates. If they were to change it for bigger updates farther apart, they would lose some of the clarity of the feedback loop, I would also worry that new items could more easily get delayed. The hard thing for me as a user is to not jump at updates when they don't affect me. I know download the updates as soon as possible, even if it is just a bug fix that I am not experiencing of a new tool that I know that I will never use i.e. the drum replacer (great tool for real drums or an audio track, but I only use midi drums, yet I still download release day one)

Good point on the fixes Chuck. Yours could well be the opinion of most; I was really just thinking out loud after a couple of difficult updates followed by one awesomely good one. I guess not everyone's 'good ones' line up though!
 
RsMcguitar you are also right about jumping onto new releases - unfortunately for me they are like chocolate in the fridge. As a Sonar tragic resistance is futile:)

ArcRex
The hard thing for me as a user is to not jump at updates when they don't affect me.

I hear you ArcRex. I too suffer thus particular afliction. A little more self control may well be all I need:)

I think the advantages of getting quick fixes and having new features introduced in more 'bite-sized' chunks greatly outweighs any higher probability of having bugs introduced by the shorter development/test cycle, assuming that's even a reality. Frankly I'm not even convinced that the monthly releases are resulting in more - or more severe - issues for more users than the yearly release did. And it's a lot easier to identify which change caused which issue when there are fewer changes in each release, and adjust settings/workflows to avoid the problem or roll back if something's a real showstopper.

I like the option of updating - or not updating - at my convenience, in between projects for example.
So the current model is a-OK for me :) 
 
What I DO miss though (strange was just thinking this this morning) is the feeling of anticipation waiting for the postal delivery with the newest Sonar boxed upgrade with install media ...

I understand why Cakewalk would aim for an update every month, given the subscription model, but I don't think they have to deliver on that.
 
I would much prefer it to be release when ready, rather than forcing it out the door, and I think this is why Cakewalk changed the naming scheme.
 
To me, 2017.02 just means the second release (update) offered in 2017, and in my mind is not tied to February specifically.
 

I'm very glad to see Cakewalk adopt the monthly release schedule yet also be sensible and pragmatic when issues are found. 
 
Speaking as software developer myself, I think regular releases are a very good thing. They help focus developers on what really matters (working software) and increase end user engagement.
 
There's a lot of developers working very hard at the moment (end of sprints can be stressful), so it is good to let them know it's appreciated.