Closed ghost closed 8 years ago
I've been saying to close old feature requests for a while now yet no one listens.
No fuck you, old feature requests are good for ideas and they cause LITERALLY NO HARM and closing them accomplishes NOTHING since general issue count means NOTHING. Count the bugs if you're gonna count anything.
Make new tag for old/unresolved feature requests. Give to old feature requests and close them. If the person is still around and cares enough, they can reopen/make a new one. For all the ones that are left closed, the new tag lets coders filter through the closed issues for them. Everybody wins.
Issue count is irrelevant and does not impede any progress. Deleting old feature requests will have no positive effect as it's just a number.
Basically what @TermedClepe and @9600bauds bauds said.
It's not hard to filter and exclude labels on GitHub.
Why keep issuecount down just for the sake of keeping issuecount down? There's no professionalism in coding for spess, and the more issues that we actually have posted, then that means they're disclosed and available to fix. There's no reason to get pissy about a number. Stop.
Why issue count being high is bad:
bloat isn't a thing
LIES
Crowding out is a thing @clusterfack , who's going to care if the amount of issues increase from 700 to 800, really, it's a small increase, but that could be 100 new exploitable bugs
add a "PRIORITY" tag to give priority to urgent issues.
@uazuaz that's [OH GOD IT'S LOOSE]
I'm also talking about bugcount as well, @clusterfack. Bugs in our code already exist, but they don't automatically appear and shouldn't force us to go into ultra-feature-freeze-lockdown mode simply because they've been documented in issues.
Just fix bugs, damn it. Edit: and try to look over your features multiple times, too.
I understand that there's tags, and people should use those tags. But I'll just chime in and say I'm randomly browsing the issues and there's basically no tags what so ever on new issues, then maybe a tag or two on everything else. Most of it, naturally, is made up of complaints and "balance requests"
The tricky thing is that Github is shit and you can't give someone tagging permissions without also giving them the keys to the entire fucking repo.
That's kind of ass. Good lord, no wonder things are in a sorry state.
What if we had a TAGBOT that read github comments from whitelisted people and automatically tagged the issue with the tags in the body of the comment? i.e. "[Oversight] [Sprite Issue]" Then only the bot wold have collaborator status. Is this doable @d3athrow?
It would be possible @9600bauds
I blame duplicate bugs, duplicate feature requests and holidays for coders. And I only condemn the first two.
Maybe feature requests should be put on the forums
it's not like there's suggestions and feedback subforums or anything
You're aware this is /vg/ you're shitposting on, not TG, right?
We have the feature freeze for a reason. Work the issues in the milestone and don't worry about the rest for now.
I'll be going through old feature requests and PRs today that are outside the milestone, still.
Can't edit comments on mobile
The issue count is not a problem whatsoever. We need to confirm that old bugs are fixed before we can close them anyways, not just close them because they're old
@mrpain666 yes, I am aware
maybe you should consider moving features and requests and "ugh I hate X feature" reports to the forums, or just the thread
I have an idea to help bring us down to manageable issue levels . . . . . . . . . . . . . . . . Close this one
Good idea!
we've got 800 and rapidly climbing.
thanks