| ▲ | eszed 5 hours 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. | ||
| ▲ | Barbing 5 hours ago | parent | next [-] | |
>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 | ||
| ▲ | tetromino_ 3 hours ago | parent | prev [-] | |
> 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. | ||