View Single Post
Old 03-10-2014, 01:03 AM   #22
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 TechniSol View Post
I strongly suspect that Kobo is depending on users installing incremental updates to get all their ducks in a row when they should be making sure all dependencies are present in each firmware since there is no guarantee of what firmware users started at and apparently not a very good mechanism in place to force necessary intermediate upgrades.(Wow, that's a long sentence...)
Kobo can't rely on that because one of their problem solving steps is "Do a factory reset". That will install the latest firmware over the original. Also, testing an install over a factory reset is a lot easier and more repeatable than testing over incremental updates. I would expect most of their development testing to be a factory reset, install latest release version and then install the test version over that. Or factory reset and install the test version.
davidfor is offline   Reply With Quote