[TYPO3-dev] passwords can't be changed in 4.2.2 backend

[Ernesto Baschny [cron IT]]

Dmitry Dulepov wrote: on 10.10.2008 13:17:

> Ernesto Baschny [cron IT] wrote:
>> 1) I think that "duplicated" bug should not be marked as resolved but as
>> CLOSED. To me, resolved means that the bug is resolved, so that I can
>> expect that a patch has been applied somewhere. This is/was not the
>> case. So I would mark duplicate entries as CLOSED, also so that they
>> don't appear twice in the later "Fixed in version 4.x.x" listing on
>> Mantis.
> 
> Stucki sets bugs to closed. We set them only to resolved. At least this
> is what I remember from the past.

Stucki (or release manager) closes all resolved items for a specific
release. But a duplicate item isn't something to be "resolved", but is
just a duplicate that we want to get rid of in our "master list" of
items that were closed for a release. So I would set it to closed and
marked as duplicate (has been reported before).

See: http://wiki.typo3.org/index.php/Bugfixing_Team, which is quite old,
but in my eyes reflects exactly my point of view:


Resolved: The bug is resolved, but not yet released to the public. It
could be in CVS (or like) waiting for a new release. Please note what
has been done and was it about to happen with the bug when putting it
into this state!


Closed: Set a bug report in this status when:
a bug is fixed and the result is released to the public.
a bug is decided not to be resolved
when it was discovered it was not a bug
when it is a duplicate (set Resolution to "duplicate")  <--



Cheers,
Ernesto