Subject: Re: How to coordinate web team for security releases?
From: Devrim GUNDUZ <devrim@CommandPrompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-www@postgresql.org
In-Reply-To: <20476.1170711517@sss.pgh.pa.us>
References: <200702051128.13819.josh@agliodbs.com>
	<20070205210315.GA7988@fetter.org>  <20476.1170711517@sss.pgh.pa.us>
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-sykmrWzzkvp0jk+3zW9A"
Organization: Command Prompt, Inc.
Date: Mon, 05 Feb 2007 23:46:42 +0200
Message-Id: <1170712002.3056.19.camel@laptop.gunduz.org>
Mime-Version: 1.0


--=-sykmrWzzkvp0jk+3zW9A
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello,

On Mon, 2007-02-05 at 16:38 -0500, Tom Lane wrote:
> * Dave (and Devrim too) making commits that made it obvious something
> was afoot.  They could and should have used the Security: filter that
> Marc set up to cause those messages to be held for moderator approval.

How? By adding a=20

Security:

line before the commit message? Does it also work for pgfoundry commits?

> * Josh using pgsql-www to notify the web team.  I had had the idea
> that pgsql-www was supposed to be closed-subscription, so I didn't
> think anything of it at the time, but that's evidently wrong.  Fixing
> that leak is the point of this discussion.=20

It should be sent to the slaves list I think, as JoshB said in his
e-mail. It is closed subscription.

Regards,
--=20
Devrim G=C3=9CND=C3=9CZ
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/


--=-sykmrWzzkvp0jk+3zW9A
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBFx6XCpme12CBXnxERAqOyAJ4heqWDL6OhiQ5StKdLh/zqzTi/rACfSa1l
1k/topAxnv+t/M0FbkMp/RE=
=c/qt
-----END PGP SIGNATURE-----

--=-sykmrWzzkvp0jk+3zW9A--