Quote:
Originally Posted by murg
Active developer interactions? If I'm remembering correctly (and I haven't gone through all the threads this morning), we've gotten 10 posts from Kobo here: - six from MDK, two announcing the release, one asking about more information about a relatively small bug (considering), one explaining the clock changes and two trying to help sven with his bricked Touch
- three from Samheer, one saying they were looking into the upgrade problem and asking people with bricked Touch's due to 2.0.0 to email him, one stating the pulling of the 2.0.0 release, and one not commenting on when requirements for resets with the new release
- and one from DarrellAtKobo, republishing Kobo's blog entry on the problems with 2.0.0.
Considering that this is a serious enough problem to require the pulling of the release, this is very little interaction from Kobo people.
And there has been very little accurate or usable communication of how to recover from the upgrade bricking your Touch. If I hadn't backed up my Touch before the upgrade, I would be very, very pissed right now. And remember, this is an upgrade that the Kobo software gave no warning about, nor allowed you to opt in or out of.
' now is giving accurate information'? |
That sounds like a pretty active line of feedback to me to be honest.
They saw complaints about the upgrade, they listened, they pulled the release and have gone back to testing.
People are having problems they gave them a DIRECT way to communicate with the guys at Kobo for support - as much as you'd love them to be posting here every 10 mins that isn't their job. They are trying to help people with actual issues by giving them a way to get help.
They have stated what they are doing to try resolve the issue.
They actively encourage real users to help test the software when they are developing it and obviously these issues didn't arise then.
I work for a software company. We make software for banks.
Sometimes we make software, test it, give it to a client and it breaks for them instantly. Does this mean we didn't test it? NO. It means they have a TOTALLY different configuration and environment with a 1000 different things on their machine than we do so it is IMPOSSIBLE, yes FULLY IMPOSSIBLE for us to test every single scenario to make sure it is fully compatible.
Did some people have problems - YES.
Do you know what was on their devices? For all you know they had corrupted books, incorrectly formatted books, they had thousands of books - it could have been anything.
It is impossible to test how something is going to work with data you dont have available.
As for giving a release date for when it would be fixed - only stupid companies did that.
A good company is going to work their ass off with the problem until they have fixed it then push it out once it has been tested.
A stupid company will give you a date then release it on that date or as near to it as possible regardless of whether it should actually be released then!