3 ms·

> Staleness is also meaningful on its own. It absolutely isn’t. Look at Mozilla’s bugzilla instead: You’ll find plenty of bugs open for years and eventually fi

by rudian 5y ago

> Staleness is also meaningful on its own. It absolutely isn’t. Look at Mozilla’s bugzilla instead: You’ll find plenty of bugs open for years and eventually fixed. Plus, stale bots don’t take Reactions into consideration. Spend a week on a popular repo and you’ll find a bunch of issues with dozens of “+1” reactions and that are closed as stale. Just because no one is working on a bug it doesn’t mean it doesn’t exist. Heck I regularly see maintainer themselves fighting the stale bot over the months. It’s hilarious to see because they do it to themselves. - closed because stale - reopened - closed because stale - reopened The only issues that could be closed automatically are those that are not reproducible and are abandoned by the author. With no further details nor “me too”s, then it’s fine to close as stale.

majkinetor 5y ago
> It absolutely isn’t. Look at Mozilla’s bugzilla instead: You’ll find plenty of bugs open for years and eventually fixed. So? Its still stale issue. Stale issue get fixes some times, but most of the time they don't. So its a metric. If you need good examples, Redmine is probably greatest example as in any major release they have something that lived 10+ years as a ticket. >Plus, stale bots don’t take Reactions into consideration. That is not true. As soon as somebody comments on my Github repo after the bot announce that issue is going to be closed soon, it resets the period to 6mo again. So this is configuration setting. I have not seen so far that somebody says something else except equivalent of "its still not resolved" just to reset the period. So now I have tickets with that last couple of years with last several comments that it is not resolved :S. Totally meaningless. > Just because no one is working on a bug it doesn’t mean it doesn’t exist. Just because ticket is closed it doesn't mean bug is resolved. I usually have some form of meta label like resultion-wontfix, resolution-done, resolution-stale... > It’s hilarious to see because they do it to themselves. Its because they didn't get it. When you repeat the same meaningless thing over and over you should question the methodology.

by rudian 5y ago

majkinetor 5y ago

> It absolutely isn’t. Look at Mozilla’s bugzilla instead: You’ll find plenty of bugs open for years and eventually fixed. So? Its still stale issue. Stale issue get fixes some times, but most of the time they don't. So its a metric. If you need good examples, Redmine is probably greatest example as in any major release they have something that lived 10+ years as a ticket. >Plus, stale bots don’t take Reactions into consideration. That is not true. As soon as somebody comments on my Github repo after the bot announce that issue is going to be closed soon, it resets the period to 6mo again. So this is configuration setting. I have not seen so far that somebody says something else except equivalent of "its still not resolved" just to reset the period. So now I have tickets with that last couple of years with last several comments that it is not resolved :S. Totally meaningless. > Just because no one is working on a bug it doesn’t mean it doesn’t exist. Just because ticket is closed it doesn't mean bug is resolved. I usually have some form of meta label like resultion-wontfix, resolution-done, resolution-stale... > It’s hilarious to see because they do it to themselves. Its because they didn't get it. When you repeat the same meaningless thing over and over you should question the methodology.