News for hackers. Stuff that matters.
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.