[Secure-testing-commits] r1671 - doc

[Joey Hess]

Author: joeyh
Date: 2005-08-27 17:03:52 +0000 (Sat, 27 Aug 2005)
New Revision: 1671

Modified:
   doc/announce.2
Log:
update

Modified: doc/announce.2
===================================================================
--- doc/announce.2	2005-08-27 15:30:48 UTC (rev 1670)
+++ doc/announce.2	2005-08-27 17:03:52 UTC (rev 1671)
@@ -35,15 +35,18 @@
 DTSA-1-1 kismet -
 XXXXXX complete
 
-Note that this announcement does not mean that testing is free of security
-issues. Several security issues are present in unstable, and an even larger
-number are present in testing. Our beginning of security support only means
-that we are now able to begin making security fixes available for testing
-nearly as quickly as for unstable. The testing security team's website has
-information about what security holes are still open, and users should use
-this information to make their own decision about whether testing is secure
-enough for production use.
+Currently, security updates are only built for the alpha, i386, ia64,
+mipsel, powerpc and sparc architectures.
 
+Note that this announcement does not mean that testing is suitable for
+production use. Several security issues are present in unstable, and an
+even larger number are present in testing. Our beginning of security
+support only means that we are now able to begin making security fixes
+available for testing nearly as quickly as for unstable. The testing
+security team's website has information about what security holes are still
+open, and users should use this information to make their own decisions
+about whether testing is secure enough for them.
+
 For more information about the testing security team, see our web site.
 <http://secure-testing.alioth.debian.org/>.