From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: pgsql-www@postgresql.org
Subject: Re: How to coordinate web team for security releases?
Date: Mon, 5 Feb 2007 14:06:28 -0800
User-Agent: KMail/1.8
Cc: Andrew Sullivan <ajs@crankycanuck.ca>
References: <200702051128.13819.josh@agliodbs.com>
	<21359.1170712469@sss.pgh.pa.us>
	<20070205215633.GA24413@phlogiston.dyndns.org>
In-Reply-To: <20070205215633.GA24413@phlogiston.dyndns.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200702051406.28769.josh@agliodbs.com>

Andrew,

> OTOH, reducing the number of addresses to include in these
> co-ordinations (since packagers presumably need to be alerted too)
> mightn't be a bad idea.

yeah, I'm thinking two (and only two) lists:
pgsql-packagers: for actual release building
press-contacts: for release FAQ.

I know the second adds more people, but I'm realizing that it's important 
that our Regional Contacts know about the releases before they go out.  
Otherwise we risk a press person actually calling, say, Nick about a 
release and having him say "what security issue?"  Also, the RCs are a 
good way to dissemenate important update information to our 
non-English-language communities.

The question is which is more appropriate for the web folks?  I'm thinking 
-packagers, because the web folks need to know when the actual packages 
will be ready and any delays.

-- 
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco