diff options
| author | Sudip Mukherjee <sudipm.mukherjee@gmail.com> | 2020-01-27 20:55:17 +0000 |
|---|---|---|
| committer | Carsten Schoenert <c.schoenert@t-online.de> | 2020-02-02 00:28:27 +0100 |
| commit | 204e82ebfe88f1243e0f7d9a424fd41a034b7f9b (patch) | |
| tree | e6ca5f60633f7d88e9cfcb043b0b9f66171bae7a /english/Bugs | |
| parent | 6fe0157ea6609afaf9875d32c5ca4eecc88d383e (diff) | |
Fix bug closing statement
Signed-off-by: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Diffstat (limited to 'english/Bugs')
| -rw-r--r-- | english/Bugs/Developer.wml | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/english/Bugs/Developer.wml b/english/Bugs/Developer.wml index 4ed047a3c03..163d34e283f 100644 --- a/english/Bugs/Developer.wml +++ b/english/Bugs/Developer.wml @@ -41,7 +41,10 @@ bug fix enters the Debian archive.</p> <p>Normally, the only people that should close a bug report are the submitter of the bug and the maintainer(s) of the package against which the bug is filed. There are exceptions to this rule, for example, the bugs filed -against unknown packages or certain generic pseudo-packages. When in doubt, +against unknown packages or certain generic pseudo-packages. A bug can also +be closed by any contributor if the bug is for an <strong>orphaned</strong> +package or if the maintainer of a package has missed closing it. It is very +important to mention the version in which the bug was fixed. When in doubt, don't close bugs, first ask for advice on the debian-devel mailing list.</p> <p>Bug reports should be closed by sending email to |