_alphaBeta_: oh, so you are handling feedback issues by yourself, or do we partition it or what? I think we should close the ones that lack necessary information and have been given a week with no feedback. I appreciate mhoram's effort in identifying the ones worth closing.

We've caught up. The system which lets us compute how much we achieved is now precisely counting issues closed/resvoled by Updaters. If you close some due to a hint from the forums, please report the amount of issues hint-closed by a person, so it can be tracked. There is a new motherbug: ⋅&nbs...

If you have more than 3 issues regarding clone tool, then it might be handy to have a motherbug for it.

-- all above here is done --
911 issues on a counter

-- all above here is done --

New mother bugs:
0004848: [motherbug] crash at startup
0004849: [motherbug] "black screen" issues

-- all above are done and counted --

We have smashed 881 bugs!

I have performed analysis of the database:

• bugs in time
• duplicate percentage
• comments in time
  

thoughts?

pati04: this has been considered. Some of us do that, but since Updaters are a bottleneck, it is more efficient for people to put information in the thread so it can be digested faster by the few who have permissions. EDIT: needs reproduction and probably a new issue report with notification of inco...

Motherbug added: 0004823: Crash in generating PNG *after* writing save on 64bit linux and windows

We have smashed 831 bugs! Well done everyone! Except people who keep duplicating bugs and adding work for us. That's not good. I stopped at the beginning of http://forums.introversion.co.uk/viewtopic.php?p=567191#p567191 @mhoram: I am not setting "related to" relations as it is unclear wh...

We have smashed 813 bugs!

I did first part of viewtopic.php?p=567112#p567112 (to "edited to add more" marker)

About unresolved issues - I asked John via secret channel. I think a texture-motherbug would make sense. A rule of thumb is that if you are considering whether to make a motherbug, it is probably worth it, because in your mind you already grouped issues by some kind of criteria. The question is whet...

-- all above are done and counted -- We have smashed 777 bugs! Who could expect that! We need to click through the issues in the Feedback state as the number of those is growing. Mostly it is 'is this still happening', which we should close after, say, a week without reply. Everything up to (and inc...

If something was reported a long time ago and we ask people to give more information or confirm that this is not happening for them anymore, because we can't reproduce, and they don't reply, then I think we will have to close it at some point. There is a close status "cannot reproduce" whi...

mazetar, you did the second pass over them ;) First pass was exciting too! I think everything that is in Feedback state should have a comment pointing out why it needs feedback. There is no need to write it up in the thread unless you have doubt. I think 2661 is a bug made early, in requirements spe...

Yeah, it is not used. I think it would be more productive to look on the issues which are in feedback state as this is where the action is right now