Rolling Updates: So we did away with annual versions of SONAR and decided to work on one version -continuously. Furthermore, end users have to try and learn a huge amount of information at once-which is much less efficient than learning features at one’s own pace over time. As developers, we’re under extreme pressure to finish a product by a certain date to meet a revenue goal – often regardless of whether it’s ready or not.Īdding a lot of features to a product in a short cycle can create problems even skilled QA teams and beta testers won’t find. ![]() This model was flawed on many levels, both for developers and end users. Some history: In the past (pre 2015), we followed a more traditional annual upgrade cycle where we released a single version of SONAR each year. For us it’s simple-it’s better for customers, it’s better for us, and we believe this way of doing business is the future, so we’re embracing it today. ![]() With the introduction of Lifetime Updates for SONAR Platinum, there have been many theories as to why Cakewalk would take such a bold move.
0 Comments
Leave a Reply. |