Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 803962E007A for ; Fri, 18 Apr 2008 06:38:51 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 90329-03 for ; Fri, 18 Apr 2008 06:38:47 -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 developer.postgresql.org (Postfix) with ESMTP id 0764A2E0066 for ; Fri, 18 Apr 2008 06:38:47 -0300 (ADT) Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and authenticated) by svr2.hagander.net (Postfix) with ESMTP id 38C4DDCCA93; Fri, 18 Apr 2008 11:38:44 +0200 (CEST) Received: from mha-laptop (localhost [127.0.0.1]) by mha-laptop.hagander.net (Postfix) with ESMTP id A1E43FF0EC; Fri, 18 Apr 2008 11:38:45 +0200 (CEST) Date: Fri, 18 Apr 2008 11:38:44 +0200 From: Magnus Hagander To: Simon Riggs Cc: pgsql-www@postgresql.org Subject: Re: What's New Message-ID: <20080418113844.28cdf7b4@mha-laptop> In-Reply-To: <1208340397.4259.63.camel@ebony.site> References: <1208340397.4259.63.camel@ebony.site> X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.0; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/202 X-Sequence-Number: 14950 Simon Riggs wrote: > We need a way to link to the release notes for the latest production > release, so people can easily see What's New. > > 1. Currently its very hard to locate a description of what the new > features in the latest release are. You have to know how the docs are > structured to find it easily. If you click on the Home Page's "Notes" > link for 8.3.1 you go to the minor release notes for 8.3.1 and there > is no obvious link to the notes for 8.3.0 which is where all the main > features are described. We don't even say that's how it works, so > there's no way of knowing you aren't viewing *all* the info. So if you > don't know, and most people don't, 8.3 looks like a minor upgrade from > 8.2 only, so why bother. Good point. But we need some way to include the release notes for the minor version as well. Do you have any suggestion for how to do it? Adding two different set of notes to the website there will just make things even more confusing, I think. Perhaps what we need is a section in the 8.3.1 release notes that says "this is a minor update. If you want to see the release notes between 8.2 and 8.3, please click here" with a link to them? > 2. There's no permanent URL for What's New in the latest release, so > people that put links to us externally need to continually update > their links. Google's What's New link points to 8.2 release notes. I > could contact them and say "Hey Google, you're wrong" but ISTM the > best way is for us to provide a permanent URL that we can then link > to from Google and our own home page. Then we only need to ask them > to do this once. This we can do, once we can decide what it should point to per your first point. But can we actually somehow control what google chooses to link to? I mean, if they detect our redirect and just link directly to the page it points to, we're right back at the same point. Or if they index them as separate pages, we'd want to make sure we get the right one. On the same tack, I've been trying to figure out if there is away to make google prefer the latest version of our docs whe nyou search for something. Now you often get hits in 7.4.. Like a way to prioritize it. Anybody know if there is a way to do that? //Magnus