maintainer and closes all the bugs marked as fixed by the upload, and the
auto-builders may start recompiling it. The package is now publicly accessible
at <ulink url="&url-incoming;"></ulink> until it is really
-installed in the Debian archive. This happens only once a day (and is also
+installed in the Debian archive. This happens four times a day (and is also
called the `dinstall run' for historical reasons); the package is then removed
from incoming and installed in the pool along with all the other packages.
Once all the other updates (generating new <filename>Packages</filename> and
<para>
The archive maintenance software will also send the OpenPGP/GnuPG signed
<filename>.changes</filename> file that you uploaded to the appropriate mailing
-lists. If a package is released with the <literal>Distribution:</literal> set
+lists. If a package is released with the <literal>Distribution</literal> set
to <literal>stable</literal>, the announcement is sent to
&email-debian-changes;. If a package is released with
-<literal>Distribution:</literal> set to <literal>unstable</literal> or
+<literal>Distribution</literal> set to <literal>unstable</literal> or
<literal>experimental</literal>, the announcement will be posted to
&email-debian-devel-changes; instead.
</para>
</listitem>
<listitem>
<para>
+<literal>derivatives-bugs</literal>: bugs reports and comments from derivative
+distributions
+</para>
+</listitem>
+<listitem>
+<para>
<literal>upload-source</literal>: announce of a new source upload that has been
accepted
</para>
</para>
<para>
Here are a few examples of valid mails used to generate news items in the PTS.
-The first one adds a link to the cvsweb interface of debian-cd in the Static
+The first one adds a link to the viewsvn interface of debian-cd in the Static
information section:
</para>
<screen>