Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 175C42E00E1 for ; Wed, 19 Mar 2008 04:29:47 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 06836-01 for ; Wed, 19 Mar 2008 04:29:41 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id 3BD332E00B1 for ; Wed, 19 Mar 2008 04:29:44 -0300 (ADT) Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and authenticated) by svr2.hagander.net (Postfix) with ESMTP id 0E106DCC960; Wed, 19 Mar 2008 08:29:42 +0100 (CET) Message-ID: <47E0C182.6020908@hagander.net> Date: Wed, 19 Mar 2008 08:32:18 +0100 From: Magnus Hagander User-Agent: Thunderbird 2.0.0.12 (X11/20080213) MIME-Version: 1.0 To: Greg Sabino Mullane CC: pgsql-www@postgresql.org Subject: Re: [ANNOUNCE] PostgreSQL 8.3.1, 8.2.7 Update Release References: <9a3dcea37bca868a2603ff077fe2c1e2@biglumber.com> In-Reply-To: <9a3dcea37bca868a2603ff077fe2c1e2@biglumber.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/392 X-Sequence-Number: 14511 Greg Sabino Mullane wrote: > >>> Release Notes: http://www.postgresql.org/8.3/static/release-8-3-1.html >>> http://www.postgresql.org/8.2/static/release-8-2-7.html > ... >> I have fixed the broken docs links in the announcement on the website. > > Now that the horse is out of the barn, could we at least put in a > one-time redirect for the links above so they aren't 404? > I'd vote against it. If we keep putting in redirects everytime someone posts incorrect URLs, we'll end up with so many redirects we'll soon enough be entirely unable to add new pages to the site... The links from the version list on the frontpage are correct, so just removing the path from the URL will bring you to the right spot - which is what I'd expect to be standard practice if you encounter a broken URL in an announcement. //Magnus