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

[Marcus Krause]

Hi!

I assume you are talking about TYPO3 core.

Peter Kuehn [wmdb] schrieb am 04.02.2009 08:47 Uhr:
> Hey yall,
> 
> what i feel noticeable about the handling of the BT is that there seem 
> to be better chances to get a more or less useless but waaaayyyy coooool 
> feature into the core than a bloody damned bug fixed, performance 
> improved or other boring routine business done.
> humanly im not unsympathetic with that, but i doubt that featurism leads 
> to the goals.

"Inspire people to share" means not only consuming but also providing 
something. I guess your (wmdb) business is (amongst others) based on 
TYPO3. So you're a consumer.
But what do you provide? I could not find wmdb in the association member 
or donations list.

Don't get my wrong, nobody has to invest in TYPO3 in any way. But then, 
do you think you are in a position to complain?
If you want to get rid of specific bugs, why don't you spend your time 
on them, provide bugfixes and send them to the core list? This would be 
helpful and highly appreciated.

If you feel unable to produce patches, just sponsor bugs. This might 
help too.


> What about that:
> could there be some sort of rule that helps to get bugs fixed and 
> improvement of existing features and code done first?
> Like "no features until existing and *acknowledged* or *assigned* bugs 
> are *not closed* that *has patch* and is *pending in core list*"?

Please do show me one project that has a clean bug trail! The goal 
should not be to eliminate all bugs but fix serious issues.
This is a common procedure in Software Development.

Also mind that fixing one bug might introduce others.


Marcus.