-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stephen Gran <[EMAIL PROTECTED]> wrote:
>> > Thus the problem is less in the development and more in the support >> > of testing requirements (all arches in sync) and stable support >> > (security response time). Therefore the N<=2 requirement is only >> > needed for tier-1 arches but not for the tier-2 which will not >> > officially release a stable. >> >> What is the detailed reasoning for this requirement anyway ? > > I thought that was fairly clear - a 12 day build of a security fix is > unacceptable, especially since it hampers getting that fix out the door > for everyone else. Then we have to adjust our security support policy. Define Tier-1 archs for security support, release updates for them first. Then for the others. I fail to see how this could be a problem. Some people here are looking for problems, when they should be looking for solutions. Please stop thinking backward. JB. - -- Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/> iD8DBQFCNeD0zWFP1/XWUWkRAl4UAKCjtZDbcu8VjqotuD3aTsQnDVIlrgCeNgkZ O0UQXl6n+bmUNIOr/wCEzJ8= =I9vA -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
