Thread: Version differences
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? 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. 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. Otherwise, we rely on the user realising that the forward/back buttons might lead to the previous release or the main index - something which is far from obvious. Thoughts? Regards, Dave.
-----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-----
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
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dave Page wrote:
> 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.
Well sure, we are one of them ;). I am not saying hide the older
releases but you don't see stuff about RHEL 3 (which is still supported)
on redhat's front page.
Sincerely,
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
iD4DBQFGvHDqATb/zqfZUUQRAjg8AKCrCeDMv7yIj6h3zMuLxisnkoqPKwCXdoMn
jQySG6hUwei2MQweiGFUww==
=fnIi
-----END PGP SIGNATURE-----
Joshua D. Drake wrote: > Dave Page wrote: >> 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. > > Well sure, we are one of them ;). I am not saying hide the older > releases but you don't see stuff about RHEL 3 (which is still supported) > on redhat's front page. No, but then you pay a lot of money for their auto-upgrade service to tell you that updates are available for RHEL3... /D
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dave Page wrote:
> Joshua D. Drake wrote:
>> Dave Page wrote:
>>>> 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.
>> Well sure, we are one of them ;). I am not saying hide the older
>> releases but you don't see stuff about RHEL 3 (which is still supported)
>> on redhat's front page.
>
> No, but then you pay a lot of money for their auto-upgrade service to
> tell you that updates are available for RHEL3...
pgsql-announce :)
Seriously. People upgrade when they feel like it, how many times do we see:
"I am running 8.1.4..., I know, I know, can you just help with this?".
I think we are wasting valuable real estate keeping the older releases
on the front page.
Joshua D. Drake
>
> /D
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
- --
=== 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
iD8DBQFGvHOtATb/zqfZUUQRAku+AJ4lxnR00CnDWbWeB3IXcKX0aW5k0ACeKu40
kcNRt2GTlB8aO4foMfFzKIs=
=yB9v
-----END PGP SIGNATURE-----
Joshua D. Drake wrote: > Dave Page wrote: >> Joshua D. Drake wrote: >>> Dave Page wrote: > >>>>> 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. >>> Well sure, we are one of them ;). I am not saying hide the older >>> releases but you don't see stuff about RHEL 3 (which is still supported) >>> on redhat's front page. >> No, but then you pay a lot of money for their auto-upgrade service to >> tell you that updates are available for RHEL3... > > pgsql-announce :) > > > Seriously. People upgrade when they feel like it, how many times do we see: > > "I am running 8.1.4..., I know, I know, can you just help with this?". > > I think we are wasting valuable real estate keeping the older releases > on the front page. Thats why we put it there - to help tell people they need to upgrade. /D
On Friday 10 August 2007 09:28, 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?
>
Honestly found the response that actually brings glee to peoples face is
pointing them toward Andrea's feature matrix. Perhaps we ought to think
about making that more official ?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
Dave Page a écrit : > 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? > I think we need to keep both. As soon as a conference is coming (say a week before), put a note about it on the announcement panel. When the conference is over, put the previous note (the latest major release one) on the announcement panel. I don't think we have enough place to put the two of them. > 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. > > 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. > If you really want to do this, best is to use the HTML files and modify them with a bunch a sed/awk/perl/bash scripting. Changing DSSSL stylesheets to build a really specific "release notes' manual" would be too hard, I guess. Regards. -- Guillaume. http://www.postgresqlfr.org http://docs.postgresqlfr.org
Robert Treat a écrit : > On Friday 10 August 2007 09:28, 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? >> > > Honestly found the response that actually brings glee to peoples face is > pointing them toward Andrea's feature matrix. Perhaps we ought to think > about making that more official ? > +1 -- Guillaume. http://www.postgresqlfr.org http://docs.postgresqlfr.org
Guillaume Lelarge wrote: > Robert Treat a écrit : >> On Friday 10 August 2007 09:28, 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? >>> >> >> Honestly found the response that actually brings glee to peoples face >> is pointing them toward Andrea's feature matrix. Perhaps we ought to >> think about making that more official ? > > +1 I offered to db:ify this and put it inside our web framework for Stefan a while ago, but he wanted to hash out the format and the way to do it a bit more on the wiki first, but the plan was AFAIK to eventually do it. The offer certainly still stands :) I can code it up (and it won't take very long once we decide how we want it), but we need several people to help fill it with content. I think one big thing to think about is how things are supposed to be sorted - right now, I don't think they're sorted at all in Stefans matrix :-) (well, they're sorted by "newest first" based on version number but within the versions they're not sorted) //Magnus
Magnus Hagander wrote: > Guillaume Lelarge wrote: >> Robert Treat a écrit : >>> On Friday 10 August 2007 09:28, 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? >>>> >>> >>> Honestly found the response that actually brings glee to peoples face >>> is pointing them toward Andrea's feature matrix. Perhaps we ought to >>> think about making that more official ? >> >> +1 > > I offered to db:ify this and put it inside our web framework for Stefan > a while ago, but he wanted to hash out the format and the way to do it a > bit more on the wiki first, but the plan was AFAIK to eventually do it. > > The offer certainly still stands :) I can code it up (and it won't take > very long once we decide how we want it), but we need several people to > help fill it with content. I can help you if you need. Regards. -- Guillaume. http://docs.postgresqlfr.org
Magnus Hagander wrote: > Guillaume Lelarge wrote: >> Robert Treat a écrit : >>> On Friday 10 August 2007 09:28, 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? >>>> >>> Honestly found the response that actually brings glee to peoples face >>> is pointing them toward Andrea's feature matrix. Perhaps we ought to >>> think about making that more official ? >> +1 > > I offered to db:ify this and put it inside our web framework for Stefan > a while ago, but he wanted to hash out the format and the way to do it a > bit more on the wiki first, but the plan was AFAIK to eventually do it. heh the way i remember that discussion was more "so figure out a way to put that in a proper database" ;-) > > The offer certainly still stands :) I can code it up (and it won't take > very long once we decide how we want it), but we need several people to > help fill it with content. I think one big thing to think about is how > things are supposed to be sorted - right now, I don't think they're > sorted at all in Stefans matrix :-) (well, they're sorted by "newest > first" based on version number but within the versions they're not sorted) no only sorted by major release and the rest of the sorting is mostly determined by the sorting it had on the releasenotes for a given major release or the order it appeared in the code (for -HEAD/8.3). But if people really like it I will certainly help with filling it with content. Stefan