4 ms·
Yeah, guess we all have different processes for dealing with reports/GitHub Issues. For me, a closed issue signals a closure of some sort, either that it's not
by diggan 6y ago
Yeah, guess we all have different processes for dealing with reports/GitHub Issues. For me, a closed issue signals a closure of some sort, either that it's not accurate, been fixed, or any other reason. Simply that time has passed does not count as "resolution" for me.
But in the end, whatever works for you!
- xboxnolifes 6y ago> For me, a closed issue signals a closure of some sort, either that it's not accurate... In this case, wouldn't it fall under being "not accurate" if the issuer doesn't supply requested information showing that it's accurate?
- diggan 6y agoNo, as I wouldn't have the full picture of the issue, I can't say if it's accurate or not.
- codethief 6y agoMaybe another status "stale" would be the solution here. That way, maintainers would be able to focus on "active" issues while the people who reported the issue could still add information to the issue later on to move it from "stale" back to "open" / "active".
- diggan 6y agoI'd reverse it and say you should have a status for when something is done discussed about, and implementation path is clear "Ready for development" or something like that. Then people who are looking for things to develop, they filter by that. Anything that is not "Ready for development" either needs triaging, or another type of closure.