Issues are being closed without fixes

[charles-cooper]

trafficstars

I noticed a lot of issues were closed just because they hadn't been fixed ("stale"). Just because an issue hasn't had a lot of activity on it doesn't mean it's not still an issue. If the goal is to find out if things are still issues, a simple ping to the issue thread asking "is this still an issue?" will do. Otherwise, this policy is just training issue reporters that the squeaky wheel gets the grease, and encourages them to make a lot of noise.

[charles-cooper]

Examples: #10108 #10917 #10897 #10512

[or2008]

+1

[gituser]

Completely agree, people are putting lots of effort into describing problems with the client, spending time on debugging and issues are being closed without a feedback from the creator.

[adria0]

Hi @charles-cooper, @or2008 and @gituser

Thanks for your comments. Yes, we decided to close most of the issues without any activity, and to be honest, yes, in a very straightforward way.

We had 400+ issues, a lot of them very old, and was really confusing how to handle them. We are still discovering how to address this, so we really appreciate your kind response about how to improve the way to do it.

Let's me explain the issues are you describing:

• #10108 : closed because was tagged as optimization and nobody worked on it for months. I absolutely agree with you that the proper way to manage this issue is first asking something like is this still an issue? or anybody working on this?

• #10917, #10897, #10512 : issue version is (2.3.8, 2.5.5), supported release versions are now 2.7 and 3.01We do not expect users working with old versions. Should we keep those issues opened or asking is the problem still exists for unmaintained versions?

[charles-cooper]

Hi @adria0 ,

For issues that were reported for old versions, I think the most efficient way to handle them is to use a script like,

This issue was reported for versions which are no longer maintained. Can you please verify this is still an issue for the release versions <a and /or b>? If we don't hear from you within two weeks we will close this issue. Thanks for your help!

[adria0]

Hi @charles-cooper,

I will send it to the devs channel, I think is, for sure, a better way to handle it. Thanks a lot for your contribution, to the project :)

[gituser]

@adria0

issue version is (2.3.8, 2.5.5), supported release versions are now 2.7 and 3.01We do not expect users working with old versions. Should we keep those issues opened or asking is the problem still exists for unmaintained versions?

Many parity users are still stuck on v2.5.13 on ETH chain because there are multiple issues with versions > 2.7 (stuck synchronization, losing peers, OOMs, etc).

Even etherscan.io is still using v2.5.13.