reopen 711815
thanks
Hi Don,
On 2013-06-10 13:27, Don Armstrong wrote:
On Sun, 09 Jun 2013, Filipus Klutiero wrote:
It is not entirely clear how archival works and why it happens.
Bugs are archived 28 days after they are closed:
http://www.debian.org/Bugs/Access
with a few additional considerations which are listed the tags which
affect archival.
They are archived both to reduce the number of active bugs which are
shown to maintainers, and to reduce the number of active bugs which can
attract spam.
Thanks. It would be nice to move (and possibly complete) this information
somewhere which can be discovered, perhaps a page on archival if nothing else
fits better.
In that case, it would be ideal to find an alternative anti-spam measure if
archival is no longer desirable. For example, mail sent to tickets which would
be archived in the current situation could require manual approval.
Or, add a heuristic which flags mails as increasingly likely to be spam as the
time since closure grows. This could be made even better by disabling this
heuristic if the sender has sent a message to the ticket before its closure.
This would not only preserve the current behavior's spam-proofness, but even
increase it. This could be generalized to a heuristic making a message's
spaminess proportional to the time elapsed since the last action on its
recipient ticket.
Since support for unarchive has been implemented, anyone with access to
control@ can unarchive bug reports, most of the disadvantages of
archival can be easily worked around.
Right, that's what I wrote. As you imply though, this workaround may be
problematic if the ITS malfunctions, and one first needs to realize that a
workaround is needed.
By the way, do not close a ticket until the bug reported was fixed.
--
Filipus Klutiero
http://www.philippecloutier.com
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
