[TYPO3-dev] The first few bugs ever ... something to do ...
David Bruchmann
typo3-dev at bruchmann-web.de
Mon Mar 8 09:31:09 CET 2010
----- Ursprüngliche Nachricht -----
Von: Francois Suter <fsu-lists at cobweb.ch>
Gesendet: Montag, 8. März 2010 08:59:37
An: typo3-dev at lists.typo3.org
CC:
Betreff: Re: [TYPO3-dev] The first few bugs ever ... something to do ...
> Hi,
>
>> In "big" projects where multiple persons are involved, you have a
>> developer who resolves the bug and then someone else (kind of a quality
>> agent for instance) who tests it and closes it if it actually works. We
>> do not have this and someone should go over resolved bugs once in a
>> while and close them.
>
> Not entirely true. It's normally the Release Manage who does this, but
> some very old bug reports may have been lost in limbo.
>
> The policy is to mark the bug as resolved when the related patch has
> been committed. It is marked as closed when the TYPO3 version containing
> the bug fix has been released.
>
Hi,
thanks for the explantation.
Is it senseful to mark old resolved bugs as closed?
My intention is that very old bugs could be closed step by step and if
required a patch should be transmitted. So perhaps after some month all
bugs with number < 1000 could be closed, later 2000 and so on.
Some items seem to arise from beginning up to now (in different
variations and locations) all the time, i.e. with entities (&, &) -
perhaps this way those bugs get eliminated one day at least inside core ...?
Best Regards
David
More information about the TYPO3-dev
mailing list