X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=html%2FDeveloper.html.in;h=4fda4b1a9944c3c55f3011faa1bc6a1869df6050;hb=747a1435ec35ebac24e9e321e6b3b4afcc2bea7b;hp=d7687c7311d092d8b18445022b9a3beb354bcd3d;hpb=74c6d03e8df9e61acb9d2fe64c5e843eba1859e9;p=debbugs.git diff --git a/html/Developer.html.in b/html/Developer.html.in index d7687c7..4fda4b1 100644 --- a/html/Developer.html.in +++ b/html/Developer.html.in @@ -3,7 +3,9 @@ $gDeveloperHtml = < $gProject - Developers' information + + @@ -36,6 +38,11 @@ and then edit the To field to say included in the default To field, because the $gBug system included it in the Reply-To. +

Where applicable, please supply a Version line in the +pseudo-header of your message when +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 mailing list, if the mailing list has been set up. @@ -84,6 +91,7 @@ the $gBug is submitted (see the instructions for reporting $gBugs), or by using the severity command with the control request server. +Separate multiple tags with commas, spaces, or both.

The severity levels are: @@ -116,24 +124,44 @@ upstream source package from which the $gProject package is derived, they should note this in the $gBug tracking system as follows:

Make sure that the To field of your message to the author -to has only the author(s) address(es) in it; put both the person who -reported the $gBug and -nnn-forwarded\@$gEmailDomain in the +has only the author(s) address(es) in it; put both the person who +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 having been forwarded to the address(es) in the To field -of the message it gets. +of the message it gets, if the $gBug is not already marked as forwarded.

You can also manipulate the `forwarded to' information by sending messages to control\@$gEmailDomain. +

Changing $gBug ownership

+ +

In cases where the person responsible for fixing a $gBug is not the +assigned maintainer for the associated package (for example, when the +package is maintained by a team), it may be useful to record this fact +in the $gBug tracking system. To help with this, each $gBug may +optionally have an owner. + +

The owner can be set by supplying an Owner line in the +pseudo-header when the $gBug is submitted (see the +instructions for reporting +$gBugs), +or by using the owner and noowner commands +with the control request server. +

Summary postings

Every Friday, a list of outstanding $gBug reports is posted to a summary @@ -148,8 +176,10 @@ $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 and to merge and unmerge $gBug reports. This is -done by sending mail to control\@$gEmailDomain. +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.

The format of these messages is described in another document available on the World Wide Web or in