[TYPO3-bugs] Discussion: Close vs. resolve in Mantis Bugtracker
Michael Stucki
michael at typo3.org
Thu Nov 6 10:12:17 CET 2008
Franz,
did you read my mail at all?
>> What else?
>
> This should not apply for extensions:
>
> | Only bugs in the current stable version will be fixed, which means
> | that you have to check if some older bug still exists in the current
> | version. Otherwise people should just upgrade.
That was exactly what I wrote. How about just saying "yes"? :-)
> The extension authors can decide by themselves for which versions they
> will still write bugfixes.
> The bug reporter shall check it with the latest version or another still
> supported version.
> I prefer to bugfix also a former version and not only the latest one, in
> order to have finally a more stable older version with less bugs than in
> a recently developed version. And some former versions of extensions are
> needed for TYPO3 3.x.
I know, that's why I wrote the same like you already.
> Is there any way to allow it to reporters that they can reopen a closed
> bug if the same error reappears again later? Or they should at least be
> allowed to enter the duplicate number by themselves.
I think they can reopen a resolved issue, but not a closed one.
However, I think that is ok this way. If a bug occurs again although it
was fixed before, this should be reported with a new issue and adding a
relation to the old bug number.
> Another new point:
> | Assign a bug to 'acknowledged' to confirm that this bug report is
> | accepted and needs fixing.
>
> This will help others to see whether a bug report is correct.
Thanks, will add it.
- michael
--
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/
More information about the TYPO3-team-bugs
mailing list