Be even more forceful about not uploading security-related updates without

consulting with the security team.

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@2539 313b444b-1b9f-4f58-a734-7bb04f332e8d

diff --git a/developers-reference.sgml b/developers-reference.sgml
index dfa6aef60b46a5e0b55e386d7ea5e4106fb760b1..dc01e2a94d108b5fbaace1c6d37e0f1b1010df9b 100644 (file)
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -6,7 +6,7 @@
   <!ENTITY % commondata  SYSTEM "common.ent" > %commondata;
 
   <!-- CVS revision of this document -->
-  <!ENTITY cvs-rev "$Revision: 1.225 $">
+  <!ENTITY cvs-rev "$Revision: 1.226 $">
 
   <!-- if you are translating this document, please notate the CVS
        revision of the original developer's reference in cvs-en-rev -->
@@ -2172,8 +2172,10 @@ security advisories, and maintaining security.debian.org.
 When you become aware of a security-related bug in a Debian package,
 whether or not you are the maintainer, collect pertinent information
 about the problem, and promptly contact the security team at
-&email-security-team; as soon as possible.  Useful information
-includes, for example:
+&email-security-team; as soon as possible.  <strong>DO NOT UPLOAD</strong> any
+packages for stable; the security team will do that.
+
+Useful information includes, for example:
 
 <list compact>
   <item>What versions of the package are known to be affected by the