Hacker News new | past | comments | ask | show | jobs | submit login

> Was this issue for an older version of Rails than is currently supported? If so, copy/paste an answer I wrote that asks if anyone knows if this affects a supported version of Rails.

No. Please do not do this blindly. It is very discouraging for the bug reporter to see their bug being ignored for a few releases, followed by this response. Example:

http://www.jwz.org/blog/2003/02/the-cadt-model/




I know it's discouraging, but sometimes, bugs get fixed as an accident of another change, or the feature was removed, or a variety of other things. Leaving it sit open with no movement at all is even _more_ discouraging.


The bug reporter reported a legitimate bug. It lies on you to act on this information. If you ignore the bug and make other random changes to the code, it still is your responsibility to fix the bug - the fact that you made it harder to find the bug by altering the code is entirely your own doing. It does not fall upon the bug reporter to test your code for bugs for every change you make. To demand this, and to close the bug when they do not comply, is entirely the wrong thing to do.




Registration is open for Startup School 2019. Classes start July 22nd.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: