I want to second this proposal.

We have the audience for such a list and they do not want to read about the 
tracker or how to secure a setup. The two testing mls have different 
purposes. testing-changes is showing packages uploaded to t-p-u, hardly a 
place for users. The other one is for general testing discussion, which I'd 
compare to -devel. Also hardly appropriate as an announcement list.
The only purpose of the new testing-security mailinglist should be to read 
announcements about testing, just like -security-announce has announcements
for stable (and oldstable when supported).

Cheers
Steffen

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to