News for hackers. Stuff that matters.
Re:How not to handle open source feedback by avar on Monday July 25, 2011 @09:37AM (#2802537)
I've had a bunch of my valid bug reports closed by Ubuntu. I've switched to Debian, and every one of them is being closed unless I go and reproduce the issue again in later versions of Ubuntu.

Some of them are general issues that won't have been fixed in later versions.

Re:How not to handle open source feedback by Luyt on Monday July 25, 2011 @10:14AM (#2802679)
jwz wrote on this:

http://www.jwz.org/doc/cadt.html

"This is, I think, the most common way for my bug reports to open source software projects to ever become closed. I report bugs; they go unread for a year, sometimes two; and then (surprise!) that module is rewritten from scratch -- and the new maintainer can't be bothered to check whether his new version has actually solved any of the known problems that existed in the previous version. "

Re:How not to handle open source feedback by j_baker on Monday July 25, 2011 @12:11PM (#2803185)
What's most annoying is the combination of this issue and the one the author writes about: the ticket sits around for a year and then gets closed a year later for some silly reason (like lack of a test program).
Re:How not to handle open source feedback by po on Monday July 25, 2011 @03:54PM (#2804316)
I'm willing to accept that a rewrite might have fixed my issue and am willing to accept a close resolution until I retest and reopen. In this case it's, "nope, I don't believe you and you're up shit-creek until you can really prove it to me."
Re:How not to handle open source feedback by jff on Monday July 25, 2011 @04:23PM (#2804443)
And your bug reports just sit there, with people popping in every few months saying they have the same problem and asking for help... but nothing ever comes of it.
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).