-----BEGIN PGP SIGNED MESSAGE----- I've got two questions about using the bug tracking system, and would appreciate your advice:
1) http://www.debian.org/Bugs/Developer says: A developer who receives a bug from the tracking system, or sees it on debian-bugs-dist, and takes responsibility for it should hit Reply in their favourite mailreader, and then edit the To field to say [EMAIL PROTECTED] instead of [EMAIL PROTECTED] (nnn-close is provided as an alias for nnn-done). Taken literally, that means I should close bug reports as soon as I acknowledge having received them; but that seems wrong to me. Am I misinterpreting the above? I also noticed that the ``Unanswered problem reports by maintainer and package'' messages periodically posted to debian-bugs-reports say: The following problem reports have not yet been marked as `taken up' by a message to [EMAIL PROTECTED] or or `forwarded' by a message to [EMAIL PROTECTED] Should I really close (`take up') each bug as soon as I accept responsibility for (eventually) fixing it? 2) I have received a text file from the bug submitter in reference to one of the ispell bugs, which I now want to forward to the upstream developer. That file is approximately 8kB in size -- not large, but if everybody added 8k example files to the BTS I suspect we'd run out of space somewhere. The only mention of size I see is at http://www.debian.org/Bugs/Reporting where it says: If they are small please include in your report any files you were using to reproduce the problem... So how small is "small"? Of course I will make note of the availability of the example file, if it's too large to include in the BTS. Thanks. -----BEGIN PGP SIGNATURE----- Version: 2.6.3a Charset: noconv Comment: Processed by Mailcrypt 3.5.1, an Emacs/PGP interface iQCVAwUBN82z5a6Bk+4xtwghAQHl+QP+O/wiEZ+5JFDQemsIILkgzcBrs6AHbs/d T60aLtjoERFrf5G49oU7ECWzqDhLByjr2X+ZyDxuGdiYDkbccsUD4yCd7uFkiPmQ 6Al76M48TMDJ0oArcl7HPqjMx3mE5an5LYHAMkpiJApcNdepyLCDzsYY02G5qwe2 9VEpfivKnEg= =XjZN -----END PGP SIGNATURE-----
