5 ms·
Realistically, for a lot of projects, if it's open for 60 days without activity it's not ever getting fixed. If anything, things like stalebot make the issues l
by ryanbrunner 5y ago
Realistically, for a lot of projects, if it's open for 60 days without activity it's not ever getting fixed. If anything, things like stalebot make the issues list match the reality of the situation more closely.
- joshmanders 5y agoThat's not true, sometimes issues get seen from notifications, not answered right away, then not revisited because it was forgotten. I've done this a few times. Sometimes a bump is a "Hey, just incase you forgot" so automatically closing is just "Ok I forgot this, but who cares now" attitude.
- Zababa 5y agoA lot of issues that ask for breaking backwards compatibility are usually going to be "treated in the next version". I'm glad most projects don't put out new incompatible versions every 60 days. The issue could stay here for a few years, to serve as a source of information and a reminder. Milestone: 2.0 is usually a good way to indicate that.
- remram 5y agoThe reality of what situation? That there are no issues?