Diana;387499 Wrote: > Hi, Mark. Can't be much of a bug if it only affects me, can it?! I > thought at least one other person might have some experience/thoughts > about it, so that we could start to scope it. > > But, as no one else seems to have the issue, it looks like I may need > to get down to some systematic solo investigation to see if there's any > pattern to it: Andy, Michael and the other developers won't be too keen > on a bug report that just says 'the track progress bar doesn't work > sometimes', will they? > > (But I suppose I could just say "Mark said I should file this!) > > ;-) > > D
LOL!! It's up to them, though, and it's really the best way they can track it. Yes, you can file a bug if it's affecting only you. They can say no or they can just ignore it, but you'll never know unless you file it, and they may never know either. Before you write a bug, though: - make sure you're running the latest version. I see 7.3.2 was released today, please install that. It would be even better if you installed the latest nightly, but since 7.3.2 was just released, the latest nightly won't be any different - though that will change as the days progress. - temporarily disable all third party plugins. These have bugs of their own, you need to isolate the problem to the core code first. - make sure it's reproducible and document exactly what you need to do in order to get this to happen. - make sure it's not due to misconfiguration on your part. - make sure it's not new, intended behaviour. Doesn't sound like it to me. - search for an existing bug first! Don't create a duplicate. - don't take it personally if the developers seem to ignore it, change its priority to minor, etc. At least it's there, what they do with it is dictated by their free time, needs and (yes) interest. I'm not a developer, but picture what it is they do when faced with a bug list (currently numbered just over ten thousand!) They do look at each and every new one and look for a duplicate. It wastes a bit of time if it's a duplicate. They look to see if the issue was solved by a recent update, this can waste time as well. Then they'll try to reproduce it on their end. If it turns out to be a misconfiguration error on the part of the bug reporter, this wastes a LOT of time. If they can't reproduce it, they may need log info from you. If they can reproduce it, it gets prioritized. If it's a quick fix, even a minor issue may get solved immediately. If it's more complicated than that, it'll get looked at in sequence according to its priority. And yes, some minor things do get left for quite some time - there are finite resources and other (perhaps much more important) bugs to work on, as well as new features. So again, don't take it personally if your bug doesn't generate a lot of activity - but at least it's documented! -- Mark Lanctot Current: SB2, Transporter, Boom (PQP3 - late beta) Stored: Boom (PQP1 - early beta), SBC (beta - no battery) Sold: SB3, Duet ------------------------------------------------------------------------ Mark Lanctot's Profile: http://forums.slimdevices.com/member.php?userid=2071 View this thread: http://forums.slimdevices.com/showthread.php?t=58399 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
