<html>
<head>
<title>$gProject - Developers' information</title>
+ <meta name="viewport" content="width=device-width, initial-scale=1">
<link rev="made" href="mailto:$gMaintainerEmail">
+ <link rel="stylesheet" href="$gWebHostBugDir/css/bugs.css" type="text/css">
</head>
<body>
included in the default <code>To</code> field, because the $gBug system
included it in the <code>Reply-To</code>.
+<p>Where applicable, please supply a <code>Version</code> line in the
+<a href="Reporting.html#pseudoheader">pseudo-header</a> of your message when
+closing a $gBug, so that the $gBug tracking system knows which releases of the
+package contain the fix.</p>
+
<p>`Done' messages are automatically forwarded to the <code>$gDoneList</code>
mailing list, if the mailing list has been set up.
<p>Make sure that the <code>To</code> 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
-<var>nnn</var><code>-forwarded\@$gEmailDomain</code> in the
+reported the $gBug,
+<var>nnn</var><code>-forwarded\@$gEmailDomain</code> and
+<var>nnn</var><code>\@$gEmailDomain</code> in the
<code>CC</code> field.
<p>Ask the author to preserve the <code>CC</code> to
-<var>nnn</var><code>-forwarded\@$gEmailDomain</code> when they reply, so that
-the $gBug tracking system will file their reply with the original
-report.
+<var>nnn</var><code>-forwarded\@$gEmailDomain</code>
+and <var>nnn</var><code>\@$gEmailDomain</code> 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 <var>nnn</var><code>\@$gEmailDomain</code> as well.</p>
+
<p>When the $gBug tracking system gets a message at
<var>nnn</var><code>-forwarded</code> it will mark the relevant $gBug as
<p>You can also manipulate the `forwarded to' information by sending
messages to <a href="server-control.html"><code>control\@$gEmailDomain</code></a>.
+<h2><a name="owner">Changing $gBug ownership</a></h2>
+
+<p>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.
+
+<p>The owner can be set by supplying an <code>Owner</code> line in the
+pseudo-header when the $gBug is submitted (see the
+<a href="Reporting.html#pseudoheader">instructions for reporting
+$gBugs</a>),
+or by using the <code>owner</code> and <code>noowner</code> commands
+with the <a href="#requestserv">control request server</a>.
+
<h2>Summary postings</h2>
<p>Every Friday, a list of outstanding $gBug reports is posted to a summary
<p>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 <code>control\@$gEmailDomain</code>.
+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
+<code>control\@$gEmailDomain</code>.
<p>The <a href="server-control.html">format of these messages</a> is
described in another document available on the World Wide Web or in
projects / debbugs.git / blobdiff