Well - there are some problems with the fast hot-fix approch.
First of all - it remains to be seen if an fast cycle (weekly) is even possible. Knowing an bit about software develeopment, I can say it’s not as simple as “fix only that thing”. Most times what seems to be an simple fix, can have serious consequences in seemingly unrelated area’s of the program. For example - an simple metronome click “repair” can have influence on the whole timing process of the program, resulting in off-timed clips, unreliable audio timing, MIDI timing, and maybe even errors in the notation part (and probably much more area’s).
Secondly - Cubase has grown far more complex than in the day’s weekly hot-fixes could be released, making fixes is not as easy as in those day’s. The result is that an longer release cycle is simply needed.
Third - an fast hot-fix cannot be tested on every hardware combination that is around. There is simply not enough time to do that! The result could be an solution for some people, and an complete wreck for others. It would be an kind of Russian roulette. People that are complaining about the supposed “beta state” of Cubase, could learn the meaning of a REAL beta- or even alpha state of software.
Taking the above in account I rather have an slower, but more tourough, state of fixes. That means not often, but more stable and reliable. Even “normal” fixes give some problems on certain systems (it is virtually impossible to test on every possible combination of hardware).
In short - I see no reason to speed up an patch process, if the result is lower quality control. This probably gives more problems than it would solve things.
This is just my opinion, not based on hard facts (I am not an musical software developer). However, I think I am not that far off…