Message-ID: <45C78CB7.9090403@kaltenbrunner.cc>
Date: Mon, 05 Feb 2007 20:59:51 +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>
	<45C789B3.1010304@kaltenbrunner.cc>
	<200702051151.30474.josh@agliodbs.com>
In-Reply-To: <200702051151.30474.josh@agliodbs.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Josh Berkus wrote:
> Stefan,
> 
>> 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.
> 
> Actually, we were discussing mechanisms to change that on -core.  Suggestions 
> are welcome.  Mostly we just want to keep a tight lid on security expoloit 
> information until the day of release.

yeah I understand the reasoning - but given the rather distributed
nature of the postgresql infrastructure I guess it might be very
difficult if not impossible to get down to less then 72 or 48 hours.
One needs that time to commit the patch and probably wait for at least
one round of buildfarm results, tag all the affected branches and build
the tarballs and finally all the packagers need to build at least the
most important binary packages.

Stefan