-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Peter Cordes <[EMAIL PROTECTED]> writes:
> [...] To get testing better tested (by providing the service more > people need to run it), and to get the security team familiar with > the soon-to-be-stable release, there could be a mechanism for > security fixes to get done on woody, etc. I don't know what kind of > security promises would be appropriate, or what, but I think it > would be a good idea to do something along these lines. Maybe > someone should make a list of packages that the security team would > take time to deal with in woody, and add packages to it over time. > Starting with popular packages and/or packages classified as > required/important might make sense. Currently, testing is getting frozen in steps as far as I understand the process. What about providing proper security updates for those parts that have already been frozen? These would have be dealt with in a special way to get upgraded anyway so you might as well provide the upgrade as a proper security update. This could also serve as a handle for the folks who are coordinating the release process. - -- Olaf Meeuwissen Epson Kowa Corporation, Research and Development GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 LPIC-2 -- I hack, therefore I am -- BOFH -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.6 <http://mailcrypt.sourceforge.net/> iD8DBQE8Q7YAFsfyfWvjfZARAn2mAKCh20XSbZlJ+wjtiOJP/zGv8z3yTwCgxOlw S0PF5uSNo7KeuY9ONzBCYl8= =FSYR -----END PGP SIGNATURE-----