Message-ID: <45C789B3.1010304@kaltenbrunner.cc>
Date: Mon, 05 Feb 2007 20:46:59 +0100
From: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
User-Agent: Icedove 1.5.0.9 (X11/20061220)
MIME-Version: 1.0
To: Josh Berkus <josh@agliodbs.com>
CC: pgsql-www@postgresql.org
Subject: Re: How to coordinate web team for security releases?
References: <200702051128.13819.josh@agliodbs.com>
In-Reply-To: <200702051128.13819.josh@agliodbs.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Josh Berkus wrote:
> WWW core team,
> 
> I need a way to coordinate with you around preparing postgresql.org for 
> upcoming releases, especially for security releases where it's critical that 
> the timing be tight.  Due to some issues with this last release, pgsql-www 
> obviously isn't the right venue.
> 
> 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.

well not that is closely related to the -www issue but the fix/patch
will end up on anoncvs/viewcvs days before the release too (and will get
published including the Security: tag and the commit message there and
distributed to the buildfarm boxes at least).
So to keep it really under the hood would probably be quite difficult to do.

Stefan