General developer forum

Just summarising some of the discussion re this topic that happened in the dev chat, for those who aren't there.

We appreciate the feedback.

The team discovered that one of the issues was closed incorrectly (one of Tim's in fact).

And that discovery led to Andrew's forum post above.

On our side we have limited resources and can't re-test every single issue. Hence we invoked the help of our remote test team to assist. A key reason for wanting to close issues we can't reproduce is the significant number of open issues in tracker and we want to reduce the 'noise' so we can better focus attention.

Clearly that process isn't perfect. Which is why the message posted when closing an issue comes with encouragement to let us know if the issue is indeed still persisting and to clarify test instructions where possible.

Ultimately though, we will need the help of all the community to make some significant inroads into this cleaning up process. Which is why I do think that Andrew's msg where the developers / community who have open issues help us check and close where appropriate, is likely the best and most effective approach to do this in a sustainable manner.

This is a process we are trying out - and hopefully we can improve it. If it ultimately doesn't work we'll try something different.

I'd welcome any community suggestions on alternative ways of doing this too.