X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=resources.dbk;h=72740732edf9d0757870041403f9c3ad3a1c52a5;hp=c4ab2eb2184254fc55dad257b5c657b790fcca25;hb=6aed2d786a9f347b606a892c201a04812b9d1caf;hpb=fc34d7250f853440f2e1a9e89c5fd34419ee0f40 diff --git a/resources.dbk b/resources.dbk index c4ab2eb..7274073 100644 --- a/resources.dbk +++ b/resources.dbk @@ -753,12 +753,6 @@ New software which isn't likely to damage your system can go directly into An alternative to experimental is to use your personal web space on people.debian.org. - -When uploading to unstable a package which had bugs fixed -in experimental, please consider using the option --v to dpkg-buildpackage to finally get -them closed. - @@ -873,7 +867,7 @@ Once the package is accepted, the system sends a confirmation mail to the 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 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 Packages and @@ -883,10 +877,10 @@ script is called to ask all the primary mirrors to update themselves. The archive maintenance software will also send the OpenPGP/GnuPG signed .changes file that you uploaded to the appropriate mailing -lists. If a package is released with the Distribution: set +lists. If a package is released with the Distribution set to stable, the announcement is sent to &email-debian-changes;. If a package is released with -Distribution: set to unstable or +Distribution set to unstable or experimental, the announcement will be posted to &email-debian-devel-changes; instead.