Listener Wrote: > > 1. Someone at SlimDevices needs to take full responsibility for making > Slimserver a stable, robust, fully tested and fully documented > software application. There is a bias toward adding features well > outside the core function of playing music. There doesn't seem to be a > commitment to adequate testing before release. That needs to be done > ASAP rather than in some future release that involves adding > functionality. SlimDevices needs to hire someone or make a current > employee responsible. I don't mean a low-level QA person; what's > needed is a project leader. > That would be Dean, and he's pretty good at it. The bias you see it elevated because new features are more fun for users to talk about. The bug fixes do get done, and not just by the paid employees. They just don't talk about them in thread after thread. ASAP is what you are getting, but clearly not as soon as demanded. 6.2.2 is the place for these fixes, but there is also a large pile of architectural fixing to be dealth with in 6.5. As an experienced developer, I'm sure you know the kind of time investment required.
That being said, times change, and demand increases for more features. currently, 567 bugs. 224 of these are actual bugs, while the remaining ones are categorised as enhancements. Of the 224, 156 are currently targetted for 6.5. Mostly this is by desire to fix, as many of them (you can take a look for yourself someime) are not yet reprducable by anyone willing/able to correct the problem in the code, and a fair number are not so much bugs in the code as akward support issues that merely need to dig into exactly what configuration flaw is the root cause. These targetted and reproducable bugs will be mostly gone by the time of release, with a few stragglers that just couldn't be fixed in time. After release, you get a flood of new bugs as always. These are due most often to configurations not yet experienced as it seems that each user is unique. I've lost entire evenings trying to replicate a bug and find I get only working results. That isn't to say that there aren't some big ones, but those aren't going to be solved by adding more managers. Your points are valid, don't get me wrong. However, this is free music software for a $300 device. i've worked for companies that make devices worth 500 times as much who can't justify that management structure to the finance department. For what its worth, I'd love to see bugzilla locked off to enhancements, the developers list closed to user requests for enhancements and a nice delays on release. However, I also know I'd go mad from the resulting furor and probably never want to see the place again. Not that long ago, I suggest in a request thread in the dev forum to leave us alone to work. The reply was less than understanding. I know you feel that this forum is anti-criticism, but its a forum. Strong reactions are standard, both ways. For now, what can be done is done. What can be added, is considered. Long term, the server is getting split up into functional chunks, but it will probably still be lacking documentation. :) My idea for the solution. Two button UI: "do what I want" and "open up a one line explanation that tells me exactly what I want and how to do it". (it's a joke....unless you have an idea how to do it) -- kdf ------------------------------------------------------------------------ kdf's Profile: http://forums.slimdevices.com/member.php?userid=7 View this thread: http://forums.slimdevices.com/showthread.php?t=20205 _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
