Okay, we're 5 mini-versions in to the new model, and I'm concerned. Yes, we've seen bug fixes each time, some great ones. But we're also seeing new bugs being shipped each time.
 
Several that affected me:
1) Drum Maps started dropping notes back in March: http://forum.cakewalk.com/Random-missing-MIDI-notes-m3190061.aspx
2) The Dorchester update seemed to do weird things with certain MIDI events, eg. playing a very short extra note before starting to play back a clip. Seems to be fixed now in Everett.
3) Everett has broken Drum Maps again - either losing the output assignment for some people, or just not playing anything back at all for me. http://forum.cakewalk.com...rum-maps-m3230072.aspx
4) Slip-editing linked clips seems to break (although maybe this is an old bug, since it seems familiar) http://forum.cakewalk.com/Slip-edit-moving-things-wrongly-m3230458.aspx
 
So right now, each month I get a bunch of new content (none of which I use, to be frank) and a 50% chance of a program-breaking bug that may not get fixed for another month. It doesn't inspire a lot of confidence and today the first chance I got at writing music for quite some time has been completely ruined by Everett not being able to play my drum VSTi. This is not what I want from a DAW and I hope that Cakewalk are going to reflect on their QA process and make sure they're not just shipping new bugs each month (and then getting the credit for fixing them later).

I totally agree with OP. It is never good for software to have fixed release schedules. Software should be released when it reaches a stable state and passes all testing, not because there is a trade fair or because it is end of month. I don't need a new version of Sonar each month, I prefer having a stable Sonar all time. New features and additional content may be nice to have, but having a stable version is essential to work with the software.
 
Even the monthly payment schedule is no reason for monthly updates. The price is mainly for using the software, not for getting something new each month. (Sure, after 12 months, a month without an update could be seen as paying for nothing for monthly subscribers, but this could be handled by separating content releases and software updates, where content is monthly, but software when it is stable.)

We will look into this issue. I'm not convinced yet that it was indeed introduced in Everett however. There were at least 2 drum map issues including crashes that *were* fixed in Everett. Keep in mind that sometimes a fix can expose a preexisting issue so its not always black and white. Everett was fully regression tested a week before release, so it had nothing to do with releasing because it was the end of the month. No company no matter how big can test every possible use case of the software and sometimes issues can slip through the cracks. 
 
Overall in Everett we fixed 40 user reported bugs including at least another 30 internally reported issues that we do not list in the bug fixes. I think that's a pretty good ratio of issues resolved in a month by any standards. Its always possible that a new issue may present itself - its the nature of software development. Keep in mind that in the old model when we released once a year, there was a way higher probability that you could get *several* new issues since there were hundreds of fixes and other changes included.
 
From an engineering point of view there is no question that the new model has way more reliability and a faster turnaround as well. 

Kylotan
Each month I get a bunch of new content (none of which I use, to be frank)

Don't know if you're tried the Sizzle Bus, but you might find it pretty useful.

If I'm not mistaken, #1 was fixed (in Dorchester or Cambridge). The waveforms moving after slip-editing isn't a new bug, as I've just explained in the thread.

Ralf, your point is invalid.  The beauty of the monthly releases is whatever is ready is released.  You're impuning things are rushed and not thoroughly tested.  I say baloney... if it's ready, release...if not, push to next month.  This model is superior to the old way by far. If 40 bugs are fixed and one or two new ones occur, I'm good with that.  Plus, it's obviouse and can be corrected quick... as per your post.
 
Every version has been better for me.  I love what's been happening.  Just look at the list.  Sorry if a favorite bug hasn't got the treatment yet, but timely fixes are great. 
 
Kylotan... Oy!  I think Noel said it eloquently. And tweaking little niggles every month rather than a yearly explosion of joy and anger is far superior.  Your logic is just shortsighted.  If several bugs relating to the Drum Maps have been solved, it's way better than waiting another year.  And thus far, this seems to be the only new issue on the table.  Compare that to the yearly releases.
 
I would imagine it's 99 to 1 staying in the current paradigm as oppose to favoring the former.  

And do remember that if a problem in a new version does bite you, at least it's painless to roll back a version: Cakewalk haven't made you use the latest downloaded (which is much appreciated, I'm sure, for cases like yours).

Great point, KPerry! all those prior fixes are still good....and catch up next month if need be!  And surfacing that new/current bug highlights it for rapid response!  50 steps forward, 1 or 2 back... is a lot of forward!

To those who are worried about monthly updates and stability and testing whatever.

You could always stay with the version you're happy with. Say X3e and upgrade when you feel the feature set and stability are right for you. Also you don't have to update every month. It's a choice.

Kylotan
Okay, we're 5 mini-versions in to the new model, and I'm concerned. Yes, we've seen bug fixes each time, some great ones. But we're also seeing new bugs being shipped each time.
 

When I first heard about the new subscription model and the monthly updates, my initial thoughts were "no way I want to update every month" and "new problems every month" ... and promptly with Braintree I ran into problems and thought "yeah, there you have it" ...
 
However, meanwhile I am fully convinced and very impressed how it actually works: 40+ fixes each month (all documented, so you know what you get), all very stable releases, never had to roll back ... and what I like best: a very open and problem-solving attitude here in the forum with Cakewalk taking part actively, which leads to fast fixes in the next release or the one after ... so it's definitely not 5 mini-versions for me.