3 ms·

The GitHub issue was "closed as not planned" due to stalebot auto-closing it, not because the maintainers actually said "we don't plan to do it". IMHO stalebot

by rmunn 3mo ago

The GitHub issue was "closed as not planned" due to stalebot auto-closing it, not because the maintainers actually said "we don't plan to do it". IMHO stalebots are an anti-feature in an issue tracker, and do more harm than good, but that's a different discussion.

subscribed 3mo ago
After 3 months. Maintainers ignored the issue for 3 months until their own automation closed it. It wasn't a rogue github bot.
- rmunn 3mo ago
  I've seen issues ignored for a lot longer than 3 months because maintainers didn't have time, then when they did have time they addressed the issue. Heck, Svelte recently did a PR fixing a bug report from about 4 years back. I'll see if I can dig it up. 3 months is not enough time, in my experience, to decide that the maintainers of an open-source project aren't interested in fixing an issue. EDIT: I'm not finding the issue that I'm thinking of very quickly. But it was a bug report from 2022 which they looked at at the time, said "yeah, this is an issue we'd like to fix but we don't have a good fix right now", and then the issue was silent. Later on, Svelte went through a major internal rewrite between Svelte 4 and Svelte 5. With Svelte 5's new internals, they were able to fix that 2022 issue. I noticed it because I had just recently read the Svelte changelog, idly clicked on some of the PRs, and noticed an issue with a very low number that was marked as fixed. But I'm not finding it now.
- watwut 3mo ago
  Which is exactly issue with stalebot. 3 months of no movement on an issue is not and should not be a reason to close it. The issue is real and this ensures it wont get fixed. Issues waiting for far longer then 3 months before they are fixed is super normal of important but not a blocker category of bugs.
  - no-name-here 3mo ago
    Claude Code has an even shorter policy. https://github.com/anthropics/claude-code/issues/16497 https://github.com/anthropics/claude-code/issues/16497

by rmunn 3mo ago

subscribed 3mo ago

After 3 months. Maintainers ignored the issue for 3 months until their own automation closed it. It wasn't a rogue github bot.

rmunn 3mo ago
I've seen issues ignored for a lot longer than 3 months because maintainers didn't have time, then when they did have time they addressed the issue. Heck, Svelte recently did a PR fixing a bug report from about 4 years back. I'll see if I can dig it up. 3 months is not enough time, in my experience, to decide that the maintainers of an open-source project aren't interested in fixing an issue. EDIT: I'm not finding the issue that I'm thinking of very quickly. But it was a bug report from 2022 which they looked at at the time, said "yeah, this is an issue we'd like to fix but we don't have a good fix right now", and then the issue was silent. Later on, Svelte went through a major internal rewrite between Svelte 4 and Svelte 5. With Svelte 5's new internals, they were able to fix that 2022 issue. I noticed it because I had just recently read the Svelte changelog, idly clicked on some of the PRs, and noticed an issue with a very low number that was marked as fixed. But I'm not finding it now.
watwut 3mo ago
Which is exactly issue with stalebot. 3 months of no movement on an issue is not and should not be a reason to close it. The issue is real and this ensures it wont get fixed. Issues waiting for far longer then 3 months before they are fixed is super normal of important but not a blocker category of bugs.
- no-name-here 3mo ago
  Claude Code has an even shorter policy. https://github.com/anthropics/claude-code/issues/16497 https://github.com/anthropics/claude-code/issues/16497