From: Joshua D. Drake <jd@commandprompt.com>
To: Dave Page <dpage@postgresql.org>
Cc: PostgreSQL www <pgsql-www@postgresql.org>
Cc: pgsql-docs@postgresql.org
Subject: Re: Version differences
Date: Fri, 10 Aug 2007 06:52:30 -0700
Message-ID: <46BC6D9E.7030505@commandprompt.com> (raw)
In-Reply-To: <46BC6812.1050808@postgresql.org>
References: <46BC6812.1050808@postgresql.org>
-----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-----
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: pgsql-docs@postgresql.org
Cc: jd@commandprompt.com, dpage@postgresql.org, pgsql-www@postgresql.org
Subject: Re: Version differences
In-Reply-To: <46BC6D9E.7030505@commandprompt.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox