Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id D0BE89FA440 for ; Mon, 5 Feb 2007 16:01:26 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 87032-06 for ; Mon, 5 Feb 2007 16:01:20 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from tinlc.com (unknown [72.18.206.65]) by postgresql.org (Postfix) with ESMTP id 0EE3D9FA06E for ; Mon, 5 Feb 2007 16:01:23 -0400 (AST) Received: from [127.0.0.1] (helo=localhost) by tinlc.com with smtp (Exim 4.60) (envelope-from ) id 1HEA4s-0002wG-St; Mon, 05 Feb 2007 15:04:38 -0500 From: "Greg Sabino Mullane" To: pgsql-www@postgresql.org Subject: Re: How to coordinate web team for security releases? X-PGP-Key: 2529 DF6A B8F7 9407 E944 45B4 BC9B 9067 1496 4AC8 X-Request-PGP: http://www.biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 In-Reply-To: <45C78B00.4020203@hagander.net> Date: Mon, 5 Feb 2007 20:04:38 -0000 X-Mailer: JoyMail 2.01 Message-ID: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/29 X-Sequence-Number: 11434 -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 > What I need is a non-public list for this, so that I can ask for web site > changes 3-4 days ahead without it becoming a news item. I think Dave's idea of -packagers works fine, there should be enough overlap. What we also need is a better way to update the mirrors in a timely manner. - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200702051500 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFFx4z6vJuQZxSWSsgRA87yAKCjB1nUqegLjvxGoRChDWPZ9RwIjwCgnYrP 9WXDio7T+nT+/Q7ODXTMKMQ= =mKwW -----END PGP SIGNATURE-----