X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=html%2FDeveloper.html.in;h=d876d91dbaa9ceec1cd07922b6b1ff0d01cb7b10;hb=766d2cb615be7df9a8f420ec418ddfedb2b3fb1d;hp=c512a7f9d0b1d04ce0ee359bde472eb9e0794abe;hpb=65150d11d2f1bcc7f6de7c3cd07be4d85842358f;p=debbugs.git
diff --git a/html/Developer.html.in b/html/Developer.html.in
index c512a7f..d876d91 100644
--- a/html/Developer.html.in
+++ b/html/Developer.html.in
@@ -36,6 +36,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 +89,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,15 +122,20 @@ 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
@@ -134,6 +145,21 @@ 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
.
+
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.
+
Every Friday, a list of outstanding $gBug reports is posted to a summary @@ -148,8 +174,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