Subject: Re: How to coordinate web team for security releases?
From: Devrim GUNDUZ <devrim@CommandPrompt.com>
To: "pgsql-www@postgresql.org" <pgsql-www@postgresql.org>
In-Reply-To: <45C78B00.4020203@hagander.net>
References: <200702051128.13819.josh@agliodbs.com>
	<45C78B00.4020203@hagander.net>
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-gGfqLXplpqjjzaumAHAo"
Organization: Command Prompt, Inc.
Date: Mon, 05 Feb 2007 23:53:35 +0200
Message-Id: <1170712415.3056.25.camel@laptop.gunduz.org>
Mime-Version: 1.0


--=-gGfqLXplpqjjzaumAHAo
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello,


On Mon, 2007-02-05 at 20:52 +0100, Magnus Hagander wrote:
> > 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.
>=20
> Will that really help? In this case, the files were uploaded to the
> ftp site long before you made your post to the -www list... Does it
> really make a difference?=20

Here is what I have been thinking about this for a while:

* As now, an announce to -packagers about the new release.

* Upload the new tarballs to a private area (instead of public FTP site)
so that only packagers and other related people can download them to
build the packages, etc.

* Win32 binaries, source tarballs and RPMs will be uploaded to another
directory (not to FTP site in developer.postgresql.org) before the
release.

* After we are done with all of them, (that takes 2 days only), we'll
move this directory to FTP site and wait for propagation.

Does it look good?
--=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/


--=-gGfqLXplpqjjzaumAHAo
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)

iD8DBQBFx6dfpme12CBXnxERAko0AJ4l5OJjdzddcUnT+qDkXzk0ZMvoYACfbTNo
qrSn5LWf2AdFLwlpvxXjnC8=
=A1Wy
-----END PGP SIGNATURE-----

--=-gGfqLXplpqjjzaumAHAo--