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

Closing inactive issues pending for >30 days #6581

Closed
gurpreet-wpf opened this issue May 13, 2022 Discussed in #6573 · 5 comments
Closed

Closing inactive issues pending for >30 days #6581

gurpreet-wpf opened this issue May 13, 2022 Discussed in #6573 · 5 comments

Comments

@gurpreet-wpf
Copy link
Contributor

Discussed in #6573

Originally posted by gurpreet-wpf May 12, 2022
Hi All,

In order to organize issues more effectively, we are planning to close the issues where minimal sample repro is not attached and which have been inactive for more than 30 days.

Any ideas/suggestions are welcome.

Thanks!

@gurpreet-wpf gurpreet-wpf pinned this issue May 13, 2022
@miloush
Copy link
Contributor

miloush commented May 14, 2022

@lindexi If there is no repro it is probably fair. It might be worth closing them with a no-repro label. People get notified and can decide what to do, including asking to re-open or filing a new issue. It would be good if there were instructions for when a repro is provided, how can people get the issue re-opened.

@Symbai
Copy link
Contributor

Symbai commented May 14, 2022

If there is no repro it is probably fair

Depends on whether a) a repro is necessary at all and b) a repro can be made and c) If people have attached a repro, this gets verified very soon and the label gets removed. For example here lindexi has attached a repro 1 day after its being tagged but label has not been removed for nearly 1 month. That means this issue would get auto closed in 2 days for no reason. Without further looking I'm sure there are more like this. So its questionable to introduce this action in the current situation.

@miloush
Copy link
Contributor

miloush commented May 14, 2022

I did not anticipate this would be an automated swipe based on existing labels. There is only a dozen issues with needs repro label.

The issue you linked I still cannot repro even with the provided executable. I'm OK with that one to be closed. #5489 on the other hand probably deserves a look. Of those issues labelled, most of them either do need a repro or could be closed.

@wstaelens
Copy link
Contributor

It is not always possible to create a repro, in a solution with 10+ projects and several 10/100-thousand lines of code,
Waiting for XPS and memory(leak) improvements 😢

@gurpreet-wpf
Copy link
Contributor Author

gurpreet-wpf commented May 16, 2022

As per the feedback received from the community, we will not be going ahead with this. Pending issues will remain active. Thanks!

@gurpreet-wpf gurpreet-wpf unpinned this issue May 20, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Jun 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants