Do you think developers willingly write bugs into their applications, then simply release them hoping they can mess up somebody's day for the fun of it?
"Allowed to roll out into production" as if there's a manager looking at the list of newly created bugs, grinning and going "This bug... I like this bug! Roll it out!"
It’s a (totally fair) attack on Signal’s lack of QA/testing in their development + release cycle.
Do they implement peer reviews on PR? Multiple reviews on changes touching mission critical code (ie. data migrations)? Do their test suites provide adequate test coverage? Do they have a manual Q/A process that involves real people testing new releases?
Considering Signal’s funding, I would hope the answer to all of those questions is yes.
But if it’s possible to release code that completely corrupts the app with no known fix, I suspect their test coverage and Q/A processes aren’t as robust as they need to be.
Microsoft got rightfully roasted for last years data loss release. This is arguably the most serious class of bug, and the most preventable.
Was there any tests for this sort of thing? surely if you are storing secure chat history to a database this should be tested to death.
Had they tested more of this functionality this serious bug would have been caught, and now that I recommended this to people, I pretty much now regret doing so for secure messaging.