On 4/16/08, Jim Popovitch wrote: > I can appreciate the significance of that situation. I don't know > that I have a solution other than to ask what does ClamAV or > SpamAssassin do in similar situations?
Dunno. Do they have to support twenty different languages? Can those translations only be started once the mainline English-language code has been frozen, because the strings in the English-language version are used as the keys for the translated versions of the strings in other the other languages? > I believe I shepherded the > idea, some time ago, of the need for a closed Mailman security team of > both developers and involved site administrators. There is one. See FAQ 1.27. It's secure enough that even I don't have access to it, although I'm sure that Barry, Mark, Tokio, and other critical people do. > I would say if a > proven trusted group of Mailman site administrators privately > discussed and tested a security fix, then I would have no problem with > fixes being committed and released at once. That's what you've got with the way RCs are handled today. > Although a "heads up!" > would be nice too. ;-) That's what you've got with the way RCs are handled today. -- Brad Knowles <[EMAIL PROTECTED]> LinkedIn Profile: <http://tinyurl.com/y8kpxu> ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
