First, thanks so much Ralph for your great effort. Given the time you have already been spending in development, you are amazingly prompt at responding to the JIRA tickets. I have also noticed your recent sprint in JIRA, great job! I am also trying to be as prompt as possible for the subjects I can help with. Though we are indeed suffering from a huge backlog, where there is plenty of room for clean up. This is a common problem in F/OSS projects – we had talked about this in the Online Drinks #1 too. There the conclusion was to keep them open, unless anybody (incl. the reporter) is stepping up to address it. That said, I am also inclined to "close" many of them due to various motivations; the reporter is not active anymore, nobody cares, the issue is not reproducible, the description is unclear, etc.
In conclusion, I follow and respond to tickets which I think are relevant. If anybody steps up to close a rusted ticket, I wouldn't mind, actually would rather be happy to see some spring cleaning. If a closed issue happens to be relevant for someone, there is nothing stopping them to re-open it. My 2 cents... On Mon, Mar 1, 2021 at 5:53 AM Ralph Goers <[email protected]> wrote: > FWIW, Jira shows 777 open issues. Somehow we need to make a dent in > these. I’m not really sure how to attack them. It seems I can only get > through 20-30 at a time. > > Ralph >
