Quote:
Originally Posted by EowynCarter
Are you a devloper yourself ?
I am, and i can easily see how the meta data could have escape them. I didn't saw it either, until such a point i tried to add new books.
True, then sould have re-tested that, to make sure it wasn't broken... Or they did and the the file name was close enough to meta data and the lack for autor / publishers wasn't noticed.
Halas one tends to be lazy with testing things that *should* not have been touched, and thus not broken.
They'll probably release a fix for that one, and everything will be back to normal.
|
Yep, I am also a developer. If you have a proper testing strategy in place and comprehensive test scripts then breaks in core functionality just shouldn't happen in release code. Bugs do happen, regressions do happen but core functionality? That implies sloppiness to me. Laziness is not an excuse. Given the profile of this release I would have thought Bookeen would have been doubly careful but apparently not.
Bare in mind that v1.9 of the epub firmware has been sold in devices for months. And that firmware was (as far as I can tell) functionally identical to 2.0.
My replies may seem harsh but I, like many others have been trying to get answers from Bookeen's piss poor customer service for months and this is, in my opinion, yet another substandard response. If this was some freebie or open source software that would be one thing but this is firmware for a device there are actually selling. A device I am currently regretting purchasing two of...
I guess I'm ranting here because at least here someone will listen
Rant officially over!
I have emailed (politely) Bookeen with my bug report and will be happy to help them in any way I can to resolve the bug and get a new firmware release out the door in the new year. I will however never buy another Bookeen device nor recommend them to anyone.