News for hackers. Stuff that matters.
Re:The sad graph of software death by elwell on Saturday January 02, 2016 @05:59PM (#10828425)
> Or in the "packrat project manager" scenario, there may be tons of low priority nice-to-have tickets that have been sitting around for months or years, even though everyone knows they'll never be worked on any time soon. If this is the case, the graph is still "sad", but it's not a death spiral... it's just a sign of a wasteful and broken issue tracking process.

What's wrong with keeping a few hundred "low priority" issues in your tracker as long as they are labeled properly?

Re:The sad graph of software death by makmanalp on Saturday January 02, 2016 @06:05PM (#10828454)
I guess what matters is: do they get tended to, cleaned up regularly, and do people get to them eventually? In my experience, the answer is usually no.
Re:The sad graph of software death by ryandrake on Saturday January 02, 2016 @10:47PM (#10829409)
If a bug has been in the software for years, and tons of people aren't complaining about it, does it really need to be gotten to eventually? Those should be resolved as "won't fix".
Re:The sad graph of software death by simoncion on Saturday January 02, 2016 @11:50PM (#10829553)
I can't agree. When I find myself in the mood, and with a bit of time on my hands, investigating -and sometimes fixing- these low-priority bugs is often a fun and useful way to spend an otherwise wasted part of a workday.
Re:The sad graph of software death by sandal on Saturday January 02, 2016 @06:18PM (#10828508)
Keep in mind this is a 500 newly opened issues over a period of four months, and that the backlog did not start at zero. So this is thousands of issues accumulating over a year.