Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id E79A09FC43D; Fri, 10 Aug 2007 10:50:31 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 28367-03; Fri, 10 Aug 2007 10:50:24 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id A68E79FC417; Fri, 10 Aug 2007 10:50:24 -0300 (ADT) Received: from [192.168.1.50] (or-67-76-146-141.sta.embarqhsd.net [67.76.146.141]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l7ADoMPp027493 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Aug 2007 06:50:22 -0700 Message-ID: <46BC6D9E.7030505@commandprompt.com> Date: Fri, 10 Aug 2007 06:52:30 -0700 From: "Joshua D. Drake" User-Agent: Thunderbird 1.5.0.12 (X11/20070604) MIME-Version: 1.0 To: Dave Page CC: PostgreSQL www , pgsql-docs@postgresql.org Subject: Re: Version differences References: <46BC6812.1050808@postgresql.org> In-Reply-To: <46BC6812.1050808@postgresql.org> X-Enigmail-Version: 0.94.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91.1/3907/Thu Aug 9 13:17:20 2007 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Fri, 10 Aug 2007 06:50:23 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/118 X-Sequence-Number: 12359 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dave Page wrote: > There is currently no way for a visitor to the website to what whats > cool and new in the latest major release. This info is in the main > announcement panel for a while after we release, but is gone as soon as > we have a conference or something. > > Any ideas how we can best fix this? Personally, I believe we should only talk about the "latest" release on the front page and have "older releases" linked. Secondly we could add a new features link after latest release that is a page about what is cool and new (with a link to everything else we have too). > Related to this, we have links on the front page to the release notes of > the latest point releases. A suggestion was made to me that these should > point to lists of all the changes in the given branch. Consider the > following scenario: > > - Critical security issue is found so we produce a release. > - Shortly after we find a simple bug in say, plpgsql that warrants > another release. > - User visits the site, and only sees the details of the bug which > doesn't affect him, thus doesn't bother to upgrade. Right. > > One solution (which could also resolve an issue that I think JD raised > recently) would be to split the Release Notes appendix in the docs into > seperate pages for each major release, re-ordered so the next/previous > links make more sense. On the website we'd then point people at these > index pages, rather than the specific release. > I like this. Joshua D. Drake - -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240 PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGvG2eATb/zqfZUUQRAjtQAKCiH8wlAgar6PNKMQ5niVd1eUqHNACgg7HN TIteNahFbjNgxZ/bPy0V5E8= =LQ93 -----END PGP SIGNATURE-----