Re: Version differences

Joshua D. Drake wrote:
> 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.

Disagree - we should be linking to the latest point releases of each
supported branch. Many people just can't do a major upgrade every year.

> 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).

On this point I'm talking about what's new in the branch rather than the
version - the next bit is about the version details.

>> 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.

:-)

/D