X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=html%2FDeveloper.html.in;h=4e14355c96a899c07b2c168e546182803004d0cb;hb=c04432ba467f7f957835b7264157951787e27f4c;hp=ab4ea80fca72ff5933b53a794c4a2f70bba015c0;hpb=c6a6851404beaa5a763fa655303e9b620af04877;p=debbugs.git diff --git a/html/Developer.html.in b/html/Developer.html.in index ab4ea80..4e14355 100644 --- a/html/Developer.html.in +++ b/html/Developer.html.in @@ -4,6 +4,7 @@ $gDeveloperHtml = < $gProject - Developers' information + @@ -38,7 +39,7 @@ included it in the Reply-To.

Where applicable, please supply a Version line in the pseudo-header of your message when -closing a bug, so that the $gBug tracking system knows which releases of the +closing a $gBug, so that the $gBug tracking system knows which releases of the package contain the fix.

`Done' messages are automatically forwarded to the $gDoneList @@ -123,14 +124,19 @@ they should note this in the $gBug tracking system as follows:

Make sure that the To field of your message to the author has only the author(s) address(es) in it; put both the person who -reported the $gBug and -nnn-forwarded\@$gEmailDomain in the +reported the $gBug, +nnn-forwarded\@$gEmailDomain and +nnn\@$gEmailDomain in the CC field.

Ask the author to preserve the CC to -nnn-forwarded\@$gEmailDomain when they reply, so that -the $gBug tracking system will file their reply with the original -report. +nnn-forwarded\@$gEmailDomain +and nnn\@$gEmailDomain when they reply, so +that the $gBug tracking system will file their reply with the original +report. These messages are only filed and are not sent on; to send a +message as normal, send them +to nnn\@$gEmailDomain as well.

+

When the $gBug tracking system gets a message at nnn-forwarded it will mark the relevant $gBug as @@ -169,8 +175,8 @@ $gBadMaintHtml

It is possible to reassign $gBug reports to other packages, to reopen erroneously-closed ones, to modify the information saying to where, if anywhere, a $gBug report has been forwarded, to change the severities -and titles of reports, to set the ownership of bugs, to merge and unmerge -$gBug reports, and to record the versions of packages in which bugs were +and titles of reports, to set the ownership of $gBugs, to merge and unmerge +$gBug reports, and to record the versions of packages in which $gBugs were found and in which they were fixed. This is done by sending mail to control\@$gEmailDomain.