public inbox for [email protected]
help / color / mirror / Atom feedFrom: Devrim GUNDUZ <[email protected]>
To: [email protected] <[email protected]>
Subject: Re: How to coordinate web team for security releases?
Date: Mon, 05 Feb 2007 23:53:35 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
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.
>
> 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?
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?
--
Devrim GÜNDÜZ
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/
Attachments:
[application/pgp-signature] signature.asc (189B, 2-signature.asc)
download
view thread (50+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: How to coordinate web team for security releases?
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox