It would be good if some information could be posted somewhere regarding who is responsible to do what with bug reports. There is some information in the sticky thread here in the beta forum, but there is a lot of questions that remains.
I'm guessing that the SqueezeCenter QA team like to do some state changes and enter some information on the bug reports and they like the bug reporter to do other state changes ? Some examples: 1. What information am I as a bug reporter responsible to provide: -- Severity ? (Or is this something the SqueezeCenter QA team will set ? ) -- Priority ? (Should I enter the priority from my point of view, or is this someone else likes to do ?) -- Target milestone ? (Should I enter when I think it should be fixed, or is this something someone else likes to do ? ) -- URL ? (What should this point to ?) -- Component ? (Should I do my best guess, or will the developers set this correctly anyway ?) 2. When a patch is provided in a bug report am I as the person who initially wrote the bug report responsible to verify the patch (if I can) ? 3. After I have verified a patch, am I responsible to change some state on the bug report or is it enough to just post a comment in the bug report that I have verified the patch ? 4. When a correction has been comitted to svn, am I as the person who initially wrote the bug report responsible to verify the correction (if I can), or is this something the SqueezeCenter QA team will do anyway ? 5. After I have verified bugreport where a correction has been comitted to svn, am I responsible to change some state on the bug report ? 6. If I provide a patch on a bug report, should I change some state on the bug report or is it enough to just provide the patch to get someone to notice that there is a possible working solution available ? The most important issues I'm personally a bit worried about: - I don't want to close bug reports which I think is corrected if this means that they will be missed when the SqueezeCenter QA team does their tests or write the release information about corrected bugs in the release. - I don't want to spend time testing things that the SqueezeCenter QA team is going to test anyway. There are of course cases where duplicate testing is a good thing, but there are also cases where it would be enough if at least one person tested it. - I don't want a correction on a bug I've written to be untested, just because I thought someone else would test it. -- 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 Database Query 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=38827 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
