farcaller on Nostr: npub1g6wqr…zf4dx I honestly don't understand the idea of auto-closing stale issues. ...
npub1g6wqr2shhl4vuhwp708qylsfhn36gqg40a35llw9hy0ewgl73wusezf4dx (npub1g6w…f4dx) I honestly don't understand the idea of auto-closing stale issues. Not on small projects, anyway. Large, too, though. I had a few actual bugs being closed on cilium repo even though I had repro steps for those.
I do understand that developers have limited capacity and they can't address every bug. But it's somewhat silly to close a bug after it was already triaged, no? You figured it's a bug, you know how to reproduce it. What is the point of closing it after? It gives me the vibe of "we don't actually give a fuck about the case that affects 1% of our customers".
The latter might be actually ok for cilium (because it's large and complex). But come on, logseq having a **confirmed case of data loss** on sync and getting a bug closed that way? wtf.
I do understand that developers have limited capacity and they can't address every bug. But it's somewhat silly to close a bug after it was already triaged, no? You figured it's a bug, you know how to reproduce it. What is the point of closing it after? It gives me the vibe of "we don't actually give a fuck about the case that affects 1% of our customers".
The latter might be actually ok for cilium (because it's large and complex). But come on, logseq having a **confirmed case of data loss** on sync and getting a bug closed that way? wtf.