| 37 |
header (don't use CC:, because that way the message's subject won't |
header (don't use CC:, because that way the message's subject won't |
| 38 |
indicate the bug number). If you are packaging so many new packages (>10) |
indicate the bug number). If you are packaging so many new packages (>10) |
| 39 |
that notifying the mailing list in seperate messages is too disruptive, |
that notifying the mailing list in seperate messages is too disruptive, |
| 40 |
do send a summary after filing the bugs to the debian-devel list instead. |
send a summary after filing the bugs to the debian-devel list instead. |
| 41 |
This will inform the other developers about upcoming packages and will |
This will inform the other developers about upcoming packages and will |
| 42 |
allow a review of your description and package name. |
allow a review of your description and package name. |
| 43 |
</para> |
</para> |
| 44 |
<para> |
<para> |
| 45 |
Please include a <literal>Closes: |
Please include a <literal>Closes: #<replaceable>nnnnn</replaceable></literal> |
| 46 |
bug#<replaceable>nnnnn</replaceable></literal> entry in the changelog of the |
entry in the changelog of the new package in order for the bug report to |
| 47 |
new package in order for the bug report to be automatically closed once the new |
be automatically closed once the new package is installed in the archive |
| 48 |
package is installed in the archive (see <xref linkend="upload-bugfix"/> ). |
(see <xref linkend="upload-bugfix"/>). |
| 49 |
</para> |
</para> |
| 50 |
<para> |
<para> |
| 51 |
If you think your package needs some explanations for the administrators of the |
If you think your package needs some explanations for the administrators of the |
Parent Directory
| 
Revision Log
| 
Patch