Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 62E789FB2B3 for ; Tue, 6 Feb 2007 05:49:31 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 45488-06 for ; Tue, 6 Feb 2007 05:49:28 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sd-2317.dedibox.fr (sd-2317.dedibox.fr [88.191.17.192]) by postgresql.org (Postfix) with ESMTP id 3B76F9FB2A6 for ; Tue, 6 Feb 2007 05:49:27 -0400 (AST) Received: from sd-2317.dedibox.fr (localhost.localdomain [127.0.0.1]) by sd-2317.dedibox.fr (Postfix) with ESMTP id 9E0F5C97B; Tue, 6 Feb 2007 10:57:09 +0100 (CET) Received: from [10.168.168.40] (ASt-Lambert-153-1-17-92.w81-249.abo.wanadoo.fr [81.249.8.92]) by sd-2317.dedibox.fr (Postfix) with ESMTP id 40969C979; Tue, 6 Feb 2007 10:57:09 +0100 (CET) Message-ID: <45C84F21.6090700@lelarge.info> Date: Tue, 06 Feb 2007 10:49:21 +0100 From: Guillaume Lelarge Reply-To: guillaume@lelarge.info Organization: PROGIMED User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Thunderbird/0.7.3 Mnenhy/0.6.0.104 MIME-Version: 1.0 To: Devrim GUNDUZ Cc: "pgsql-www@postgresql.org" Subject: Re: How to coordinate web team for security releases? References: <200702051128.13819.josh@agliodbs.com> <45C78B00.4020203@hagander.net> <1170712415.3056.25.camel@laptop.gunduz.org> In-Reply-To: <1170712415.3056.25.camel@laptop.gunduz.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.47 tagged_above=0 required=5 tests=AWL, BAYES_40, RCVD_IN_NJABL_DUL X-Spam-Level: X-Archive-Number: 200702/90 X-Sequence-Number: 11495 Devrim GUNDUZ a ecrit le 05/02/2007 22:53: > 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? It looks good to me if these are the steps to follow for security release only. I update the french manual for each release (even minor ones). Last week, I had some hints that a minor release was going to happen and I kept an eye on the ftp source server (as I do every time a minor release is on its way). Saturday, 7.4, 8.0 and 8.1's french manuals were updated on the SVN repository (see http://svn.postgresqlfr.org/timeline?from=02%2F03%2F07&daysback=0&changeset=on&update=Update). And Sunday, 8.2's french manual was updated (see http://svn.postgresqlfr.org/timeline?from=02%2F04%2F07&daysback=0&changeset=on&update=Update). Sunday evening or Monday morning (I don't quite remember), I uploaded them. I completely understand why you want a private area for security updates. French manual will be available a few days later. But I don't think other releases should take the same steps. I translate beta and RC because it gives me much more time to do it. Actually, I have a full translation available the same day the release is out. And if it was possible that I have access to this private area, it would be great :) -- Guillaume.