View Single Post
Old 03-17-2012, 07:02 PM   #54
jgsmith
Connoisseur
jgsmith ought to be getting tired of karma fortunes by now.jgsmith ought to be getting tired of karma fortunes by now.jgsmith ought to be getting tired of karma fortunes by now.jgsmith ought to be getting tired of karma fortunes by now.jgsmith ought to be getting tired of karma fortunes by now.jgsmith ought to be getting tired of karma fortunes by now.jgsmith ought to be getting tired of karma fortunes by now.jgsmith ought to be getting tired of karma fortunes by now.jgsmith ought to be getting tired of karma fortunes by now.jgsmith ought to be getting tired of karma fortunes by now.jgsmith ought to be getting tired of karma fortunes by now.
 
Posts: 75
Karma: 233442
Join Date: Dec 2009
Location: Toronto, Canada
Device: Sony PRS-600, Kobo Touch, Kindle PW2
Quote:
So, how to point out the bugs in your opinion? I didn't notice any bug tracking tool or a questionnaire... And yes, over 3 months just to fix some bugs (and to add some new) it's disappointing.
I'm not sure many people realize some of the complexities of software development. For example:
- Kobo has several devices, and each device requires both maintenance (support) and new features (development)...not just the Touch
- In order for the software to be manageable, I suspect Kobo tries to keep a single set of source code across all devices where possible. Having to add the same function to each device individually would be cost-prohibitive and would just get passed on to the consumer.
- Most software shops stick to a regular schedule for software releases. Time for requirements gathering (defects + new features); time to design the changes; time to develop the changes; time to test the changes internally; time to beta test the changes with the community. This all takes time. 3 months is very typical.

I've been working in software for 25 years, so I could go on...
jgsmith is offline   Reply With Quote