On Tue, Dec 20, 2005 at 04:34:05PM -0500, micah wrote: > Additionally, AJ references his blog post[2] that discusses work he has > been doing to create embargoed vs. unembargoed queues for > security.debian.org. I have been working with him to test out his > changes and to take notes on the processes and quirks involved. This > goes a long way towards allowing for testing-security to use > security.debian.org queues instead of the alternative queues that we > currently have setup. This is beneficial for a number of reasons. Some > of them include: eliminating the need for the user to have to know Yet > Another Apt Source (YAAS); allows for the testing-security team to be > more officially underneath the project umbrella; and clears the way for > the possibility of having one Security Team (instead of two) separated > only along public vs. embargoed lines, rather than stable vs. testing.
- Allowing automatic propagation of security fixes from testing-security to testing-proposed-updates *and* unstable Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
_______________________________________________ Secure-testing-team mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/secure-testing-team
