[TYPO3-dev] Bugtracker - What is it good for?

ries van Twisk typo3 at rvt.dds.nl
Thu Jan 8 19:03:31 CET 2009


On Jan 8, 2009, at 12:01 PM, Steffen Kamper wrote:

> Hi,
>
> Peter Klein schrieb:
>> I was wondering if posting on bugs.typo3.org have any effect?
>> Or do I also have to post the bugreports in other places? (corelist
>> etc.)
>>
>> Some of the bugs I have reported is over 2-3 years old, but still
>> haven't been fixed.
>>
>> (That's the reason why I don't upload patches to the bugtracker)
>>
>
> wrong! You should always report bugs to the bugtracker, if you have a
> patch always upload!. This is
> * only chance to get it fixed
> * mandantory for core RFCs
>
> Me and many others always read bugtracker, but of coarse not all are  
> the
>  one i pick to examine, it often depends on some things like
> * detailed description
> * description how to reproduce
> * having a patch
>
> If all 3 criterias are present, bug has good chance to be reviewed,  
> also
> entries with comments. So it's useful if others comment bugs also like
> * i can confirm, same behaviour here
> * i found out that when i [...] situation change in [...]
> etc.
>
> If there is a bug that seems to be forgotten, then its good to place a
> reminder on this list.
>
> vg Steffen

It might not be a bad idea to close all open bugs in bugtrack older  
then 1 year,
specially when there was a patch attached. There is a good change that  
the patch will not work anymore anyways.

This will specially raise awareness to the people who did send in a  
bug. If they are not interested anymore,
then they stay closed (and un-resolved??) if there is interested from  
the reporter then communication can start again.

I have one open still from 24-2-2005, I mean just close the damn thing  
if there is no interest!!!

Ries








More information about the TYPO3-dev mailing list