News for hackers. Stuff that matters.
Re:How not to handle open source feedback by ecaron on Monday July 25, 2011 @09:41AM (#2802549)
I'm pretty sure every OS follows this practice, here's my personal example from Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=219715
Re:How not to handle open source feedback by silvestrov on Monday July 25, 2011 @10:10AM (#2802659)
Not my experience with Apple: I've had years-old bug reports where Apple suddenly emailed me and asked me to confirm that the bug was fixed in the latest developer preview (for an major OS version later).
Re:How not to handle open source feedback by hboon on Monday July 25, 2011 @10:55AM (#2802842)
Same experience here, I have 2 year old bugs fixed 2 major version later.

Unfortunately the official bug report system is opaque though.

Re:How not to handle open source feedback by smackfu on Monday July 25, 2011 @03:20PM (#2804159)
Unfortunately the other common case for Apple is that your bug just gets marked as a duplicate, and since you only have visibility to the bugs you opened, you lose all tracking.
Re:How not to handle open source feedback by DrJokepu on Monday July 25, 2011 @09:29PM (#2805566)
Filing a bug for Apple is worth the effort even if they mark it as duplicate. Duplicate reports count as "votes", the more people file the same bug the higher priority it enjoys. Apple employees mention this regularly on the Apple Developer Forums and encourage everyone to file bugs.
Re:How not to handle open source feedback by streptomycin on Monday July 25, 2011 @10:19AM (#2802696)
To be fair, testing a hardware-specific bug is a bit more complex.
Re:How not to handle open source feedback by lamby on Monday July 25, 2011 @12:00PM (#2803131)
In case it wasn't clear from the parent, Debian doesn't do this (at least not automatically).