Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

document growing issue count #4555

Merged
merged 1 commit into from
May 24, 2022
Merged

document growing issue count #4555

merged 1 commit into from
May 24, 2022

Conversation

matkoniecz
Copy link
Contributor

BTW, I think I would wontfix #2958 #2986 #2704 #3692 #3849 #3491 #3958 #3264 #3961 #3782 as not worth doing, not improving things or outright impossible

Copy link
Collaborator

@imagico imagico left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

In general i would suggest to all maintainers to try find the time to look over open issues and try to work on building consensus to close some of them. I usually make a comment 'suggest to close this' where i have the impression this would be a good idea.

I created two new label - wontfix-unfeasible Issues closed because of lack of suitable solution and hard hard problem that is difficult to solve - that can be used to classify some of the issues you linked to.

Copy link
Collaborator

@pnorman pnorman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Accurate, but I'd like to work out a path to getting it back under 300.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants