CorOS 2.0.2 is now available

Quad Cortex
45

I’d say, that’s not the point.

When a critical, security related bug is discovered in a release, then usually a “hotfix release” happens. At least that’s what most dev teams call it. A hotfix is by definition based on the last release and fixes only the critical issue. Nothing else is touched. Dev tool support for that is pretty good. When doing this properly, the likelihood of breaking something unrelated (preset renaming) is very low. Not zero, but very low. So my assumption is, that there is no proper hotfix process established at NDSP.

Usually some automated test suite is in place in professionally run software projects. It’s harder when hardware is involved, but not impossible. Any automated test suite would contain such a basic feature like preset renaming and would discover any breaking changes. The automated suite is (as a minimum) executed before each release, but ideally more often. For example in what software developers call “nightly builds”. The fact that this bug could make it into a hotfix is a clear indicator that there is no automated test suite at all or an insufficient test suite.

Not a good look for a company that makes most of their revenue from software in 2023.

7 Likes
46

Agreed, and automation testing is literally my job.

In the wider industry it is often still an uphill battle to get test automation prioritised, as product managers and others often don’t see an immediate benefit or return in the time spent doing it. Testers can have a tough time constantly pushing for it, as ‘shiny new features’ are seen as a higher priority. I know I’ve had that exact issue in the past.

Hopefully if that is the case here, then they will have a rethink and put some time into automation testing, which would hopefully in turn speed up the development process overall as testing time is reduced.

2 Likes
47

i don´t want to make this a discussion and go back and forth and while i agree someone smart would not update prior to a gig and such but that´s just a recommendation for knowledgeable users to do. It is entirely the companies responsability. You cannot blame users, paying users for not expecting the unexpected

2 Likes
48

Having been working with recording software for a long time, it’s just always been common knowledge to me, and I thought anyone else too.

New versions of a DAW could often break plugin compatibility… new versions of an OS could stop DAW’s working etc.

It is absolutely still a company’s responsibility to release good software, I just know how often they don’t.

49

hence why it is their fault and their responsibility . not the customers fault for updating fast or not knowing something.
I´m glad we finally agree. have a blessed day.

1 Like
50

I think this thread has run its course.

2 Likes