Christopher, some thoughts: 1. Some ideas to make the long bug list today easier to use - Maybe the "Target milestone" field could be part of the list result, today you can see STATUS in the list result but that doesn't tell me which release a bug/enhancement is scheduled to be corrected in. - Maybe it would be good to have a easy way to search for "just open bugs" or "just open enhancements", today you have to use the advanced search mechanism to do this.
2. When we are talking about feedback on bugs I have often felt that reporting a bug is like putting the problem in a box which won't be opened for a long long time. One thing that would probably be a lot better even though its probably isn't so much work would be if the process was: Step 1: A bug is registered by the user: STATE=NEW Step 2: SlimDevices/Logitech reads the bug checks that the information provided seems to be enough, adds any additional information and changes the state or some other field to indicate the the bug has been recieved. Maybe also give some prelininary indication if the bug will be corrected in the maintenance release (6.5.2), the current development release (7.0) or in some future release. Step 3: A notification is sent from the bug tracking system to the user that registered the bug. Step 4: Some time passes by Step 5: Some developer starts to work on the bug, reproduces the problem and solves the bug. I think the critical feedback is at step 3, my experience so far is that that indication can take a long time. The reason is probably because you are trying to do too much investigations before giving feedback. As a bug reporter I would be happy with just some sort of indication that someone has seen my problem, this would also increase my interest to report more bugs in the future. 3. Do you want regular users to report bugs, or is it better that they contact regular support with their problems ? 4. As you probably already is aware of people are sometimes using the discussion forums for support issues when they ought to contact the support organisation instead. Maybe it would be a good idea to have a sticky thread or something in the discussion forums that describes when you should contact the support organization instead of the discussion forum ? I guess this is basically one thing you are trying to do with this thread. 5. What about correcting bugs ? If you have reported a bug and it is planned to be corrected in a future release. If the bug reporter is a developer, would a patch for the bug attached to the bug report result in that the bug can be included in an earlier release ? If a patch is provided some time after the bug was reported will this be automatically be picked up by someone at SlimDevices/Logitech or is some other type of notification also required for the patch to be noticed ? -- erland Erland Isaksson 'My homepage' (http://erland.homeip.net) 'My download page' (http://erland.homeip.net/download) (Developer of 'TrackStat, SQLPlayList, DynamicPlayList, Custom Browse, Custom Scan, Custom Skip, Multi Library and RandomPlayList plugins' (http://wiki.erland.homeip.net/index.php/Category:SlimServer)) ------------------------------------------------------------------------ erland's Profile: http://forums.slimdevices.com/member.php?userid=3124 View this thread: http://forums.slimdevices.com/showthread.php?t=33033 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
