Hacker News new | ask | show | jobs
by eszed 82 days ago
Sure. So try to reproduce on a current build, and close with a "No longer reproduceable on ___". That'd be good practice. Closing silently because no one can be bothered to evaluate at all is horrendous, and creates the user expectation that "no one looks at these, so I'm not going to keep reporting it" which "justifies" developers closing old bugs.
2 comments
Barbing 82 days ago
>creates the user expectation that "no one looks at these

Apple has done the best job of creating this expectation.

Apple Feedback = compliments (and ideas)

Public Web = complaints & bug reports

Apple Support = important bug reports (can create feedback first then call immmediately)

—

Prev comment w/link (2mo ago): https://news.ycombinator.com/item?id=46591541

link
tetromino_ 82 days ago
> try to reproduce on a current build

Good luck doing that when the bug report (like virtually all bug reports in nature) doesn't provide sufficient reproduction steps.

link
eszed 82 days ago
I agree with you about that, but why would an ill-defined report be kept open in the first place? It shouldn't be. Give the user an opportunity to provide more detail - for my own use I have some auto-text "scripts" set up, to make prompt questions easy - and then auto-close after a few days.

[Edit, answering my own question: they're left open because they were ignored to begin with.]

I write excellent bug reports, the vast majority of which (I'm thinking of one service-provider in particular, may they live in shame) get ignored. Or escalated and ignored; somehow that feels worse, though I don't know if it should. I guess it's the hope. It's the hope that kills you.

link