On 01/18/2011 09:44 AM, Karsten Bräckelmann wrote:
--- Comment #4 from Warren Togami<[email protected]> 2011-01-17 22:20:21 UTC
---
This isn't fixed until it is pushed to the sa-update channel.
I don't want to start an edit-war, so I keep the bug in the REOPENED
state. However, I *do* want to clarify that sentence as-is is wrong.
Resolved FIXED means in code.
The equivalent, a bug targeted for $release, is resolved once the code
is in the appropriate branch, and voting has been done if required. It
does not remain open until an actual release.
Please pardon me, but I must respectfully disagree that we should
consider this "FIXED" if it is fixed in code. I understand where you
are coming from. While I personally am not effected by this issue (no
Russian users), I fear such a status could be confusing and upsetting to
the user who submitted this bug report and others effected by the issue
who look at the bug report.
In any case, I looked at update-rules-3.3 as JM suggested would work. I
think I know how it works. But I dare not run it without clarification
from JM (which server to run it upon, what user, what directory) because
I don't want to screw up the production sa-update channel. I haven't
heard back from JM.
Warren
