[TYPO3-core] Resolving vs. Closing bugs

Martin Kutschker Martin.Kutschker at n0spam-blackbox.net
Tue Jun 6 13:56:31 CEST 2006


Michael Stucki schrieb:
> 
> There is one thing that I have noticed in the bugtracker: Many bugs have
> been set to "closed" when they have been fixed. In the past however it was
> our practice to set them to "resolved".

I closed all bugs where the bug submitter acknowledged the solution.

I have also closed bugs whose nature were support request, user errors or 
rants.

> - When a bug has been fixed in CVS, we set it to "resolved" so that people
>   can see that it is fixed in the upcoming version

Didn't thought about that when employing my policy. You're right.

> - Closed bugs are by default filtered out: There is a risk that people
>   won't find the bug and therefore report duplicate issues more often.

I didn't manage to filter out resolved bugs consistently. I'm wading in 
them ;-)

> - Future: The correct handling would be that a bugfix once released should
>   be set to "closed". This means that after releasing 4.0, all bugs that
>   were set to "resolved" can now be closed.

Please!

>   However, since I don't want to click 1000 times for this, this has not
>   been changed yet... (ideas?)

Get a gun, point it to the head of a person with DB access and force him to 
  write an appropriate UPDATE statement :-)

Masi



More information about the TYPO3-team-core mailing list