Thread: Firmware 4.7.10413
View Single Post
Old 12-26-2017, 09:19 PM   #77
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by the.Mtn.Man View Post
This is what baffles me about Kobo firmware development. They've been hammering on this thing for years and should have a rock solid operating system at this point that only needs a little fine-tuning now and then, but instead there are major bugs that have persisted across firmware releases (for instance, the two-finger light adjustment on the 1st generation Aura has been screwed up one way or another in every single release after 3.12.1), and it seems like every new release ships with significant new bugs that should have been caught during testing.
Simple: because it's hard.

The more code you have, the more interactions there are. The more likely you are to make a change that has an unintended consequence. Or, that to fix something you don't have any choice but to break something else. Then you have to decide on importance and when to do things.

As to seeing bugs before release, yes, they should be testing. And they are. But, a full suite of tests can take a long time. And as an example of how hard it can be to see bugs, the stats problem wasn't noticed here for a full week. The nature of the bug meant the critical people here didn't notice it for a week. And I'm not surprised it wasn't something a tester didn't see. And I have a suspicion about how the bug came about, and if I'm right, I'm not at all surprised (think the unintended consequences of other changes).
davidfor is offline   Reply With Quote