Aryabhata <[email protected]> writes: > Thank you for the response, and my apologies if my initial email came > across as a request for someone else to do the heavy lifting! That > definitely wasn't my intention. > > My question was driven purely out of curiosity regarding how the project > manages deep legacy PRs. I wasn't sure if there was a specific project > policy to keep them open as historical documentation, or if they just > simply hadn't been touched in a while due to more pressing priorities. > > I completely understand that bug triage takes a massive amount of effort. I > am more than happy to read through the list myself and see if there are any > I can assess or test on my end, though my expertise might be limited on > issues.
It is hard, and it often takes the ability to tell the submitter they need to udpate to the latest version, retest, and file better debug info. And then it's a judgement call to close as unfounded/no-longer-reproducible. It's not super fun to grovel over bugs, especially if the bug report doesn't come with substantial investigation from the submitter. That tends to lead to them just staying open.
