[TYPO3-bugs] Discussion: Close vs. resolve in Mantis Bugtracker
Franz Holzinger
franz at fholzinger.com
Thu Nov 6 07:57:50 CET 2008
Hello Michael,
> Hi Franz,
>
>> Is this a recommendation only for the TYPO3 Core or also for TYPO3
>> extensions on the bugtracker?
>> I think that some points should not be required for extensions.
>
> Which ones? After looking at this list, I only see one point which I
> think should be removed:
>
> | 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.
>
> 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.
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.
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.
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.
- Franz
More information about the TYPO3-team-bugs
mailing list