https://bugzilla.wikimedia.org/show_bug.cgi?id=19161
MZMcBride <b...@mzmcbride.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |b...@mzmcbride.com
Resolution|FIXED |
--- Comment #45 from MZMcBride <b...@mzmcbride.com> 2011-04-01 15:40:43 UTC ---
(In reply to comment #44)
> I've opened Bug #28366 and Bug #28367 to address the issues you've raised.
I've resolved both of those bugs as invalid.
> If you want the current solution completely reverted, I suggest you open a new
> bug to that effect. I recommend you look at Bug #542 (fixed, closed) and
> later
> bugs like Bug #27527, Bug #28182, etc for an example of how to log issues of
> problems that fixing a bug creates.
No, this is the bug tracking this problem. If this bug hasn't been adequately
addressed, it should remain open.
> Even if you disagree with the fix and think it is the wrong thing to do,
> reopening this bug is not appropriate. The fix is done. It has been applied
> and deployed. It is appropriate to *file a new bug* if you think the old
> behavior should be restored. Re-opening an old bug is not the correct way to
> address the current situation.
Your assumption that "the fix is done" is flawed. The fix isn't done because it
didn't resolve this bug adequately. This bug needs to remain open until this
issue is properly addressed.
>> Avoid creating data that you want to remain hidden.
>
> If you think that is what is needed, I suggest opening a new bug to that
> effect.
This bug is about limiting what data is propagated and in what circumstances.
There's no need for a separate bug.
Re-opening this bug.
--
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
