Thread: Reading Progress button moved?
View Single Post
Old 11-19-2019, 09:55 PM   #19
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 rashkae View Post
Considering some of the *other* bugs Kobo has let sit for several months over multiple firmware releases, I would hardly call this one "central".

I would be thrilled if Kobo took any kind of care with releasing regression fixes, but unless it's absolutely critical, (ie, people can't buy books for their store or are returning them,), just about any bug fix gets rolled into the next feature release, with a whole new set of bugs to go with it.
Kobo have pulled releases and released quick updates several times. But, I don't think I have seen a single one that was because of a problem with the store. All of them have been in cases where people couldn't read their books, or the performance was so bad the devices were unusable. Where they are in the rollout cycle when it is reported probably also has an affect on whether they will release a quick fix. As would what their plans for when the next release is (6months? quick fix. Next month, wait).
davidfor is offline   Reply With Quote