Thread: Updates "What's New" URL
Hi, I have a patch that updates "What's New" URL to point to the 9.2 release notes (see attached). One reason I'm commenting on this trivial change is that it is something we do need to remember to do every release. Perhapsthere might be an easier method to update the "What's New" page, perhaps having it point automatically to the newversion of the release notes once we release? Jonathan
Attachment
Hi,
I have a patch that updates "What's New" URL to point to the 9.2 release notes (see attached).
One reason I'm commenting on this trivial change is that it is something we do need to remember to do every release. Perhaps there might be an easier method to update the "What's New" page, perhaps having it point automatically to the new version of the release notes once we release?
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Tue, Sep 25, 2012 at 3:21 AM, Jonathan S. Katz <jonathan.katz@excoventures.com> wrote:Hi,
I have a patch that updates "What's New" URL to point to the 9.2 release notes (see attached).Thanks - I've committed and pushed it. The change should show up soon.
One reason I'm commenting on this trivial change is that it is something we do need to remember to do every release. Perhaps there might be an easier method to update the "What's New" page, perhaps having it point automatically to the new version of the release notes once we release?Doesn't seem unreasonable.
On Sep 25, 2012, at 8:26 AM, Dave Page wrote:On Tue, Sep 25, 2012 at 3:21 AM, Jonathan S. Katz <jonathan.katz@excoventures.com> wrote:Hi,
I have a patch that updates "What's New" URL to point to the 9.2 release notes (see attached).Thanks - I've committed and pushed it. The change should show up soon.Hm, not showing up for me yet, perhaps it's still in varnish?
One reason I'm commenting on this trivial change is that it is something we do need to remember to do every release. Perhaps there might be an easier method to update the "What's New" page, perhaps having it point automatically to the new version of the release notes once we release?Doesn't seem unreasonable.One alternative thought - we setup something in the docs that's a URL i.e. http://www.postgresql.org/docs/current/static/release-notes/ (or /whats-new/) that just links or redirects to the current release notes. Perhaps there is some coding magic we can do to find the latest release from that
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Tue, Sep 25, 2012 at 3:13 PM, Jonathan S. Katz <jonathan.katz@excoventures.com> wrote:On Sep 25, 2012, at 8:26 AM, Dave Page wrote:On Tue, Sep 25, 2012 at 3:21 AM, Jonathan S. Katz <jonathan.katz@excoventures.com> wrote:Hi,
I have a patch that updates "What's New" URL to point to the 9.2 release notes (see attached).Thanks - I've committed and pushed it. The change should show up soon.Hm, not showing up for me yet, perhaps it's still in varnish?Fixed now.One reason I'm commenting on this trivial change is that it is something we do need to remember to do every release. Perhaps there might be an easier method to update the "What's New" page, perhaps having it point automatically to the new version of the release notes once we release?Doesn't seem unreasonable.One alternative thought - we setup something in the docs that's a URL i.e. http://www.postgresql.org/docs/current/static/release-notes/ (or /whats-new/) that just links or redirects to the current release notes. Perhaps there is some coding magic we can do to find the latest release from thatWell we have the version info in the database iirc. See the Versions model. Patches welcome :-)
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
<p dir="ltr"><br /> On Sep 25, 2012 7:27 AM, "Dave Page" <<a href="mailto:dpage@pgadmin.org">dpage@pgadmin.org</a>>wrote:<br /> ><br /> ><br /> ><br /> > On Tue, Sep 25,2012 at 3:21 AM, Jonathan S. Katz <<a href="mailto:jonathan.katz@excoventures.com">jonathan.katz@excoventures.com</a>>wrote:<br /> >><br /> >> Hi,<br/> >><br /> >> I have a patch that updates "What's New" URL to point to the 9.2 release notes (see attached).<br/> ><br /> ><br /> > Thanks - I've committed and pushed it. The change should show up soon.<br /> > <br /> >><br /> >><br /> >> One reason I'm commenting on this trivial change is that it is somethingwe do need to remember to do every release. Perhaps there might be an easier method to update the "What's New"page, perhaps having it point automatically to the new version of the release notes once we release?<br /> >><br/> ><br /> > Doesn't seem unreasonable. <p dir="ltr">As a first step, did you put it on the wiki page (inthe pgweb project) that lists which steps should be made for each major release? Since its something that only happensonce a year, and we have to change a bunch of other pages (such as which docs versions exist) then anyway, I thinkit's acceptable to have it as a manual process. (i won't stand in the way if someone wants to automate it of course...)<p dir="ltr">/Magnus <br />
On Sep 25, 2012 7:27 AM, "Dave Page" <dpage@pgadmin.org> wrote:
>
>
>
> On Tue, Sep 25, 2012 at 3:21 AM, Jonathan S. Katz <jonathan.katz@excoventures.com> wrote:
>>
>> Hi,
>>
>> I have a patch that updates "What's New" URL to point to the 9.2 release notes (see attached).
>
>
> Thanks - I've committed and pushed it. The change should show up soon.
>
>>
>>
>> One reason I'm commenting on this trivial change is that it is something we do need to remember to do every release. Perhaps there might be an easier method to update the "What's New" page, perhaps having it point automatically to the new version of the release notes once we release?
>>
>
> Doesn't seem unreasonable.As a first step, did you put it on the wiki page (in the pgweb project) that lists which steps should be made for each major release? Since its something that only happens once a year, and we have to change a bunch of other pages (such as which docs versions exist) then anyway, I think it's acceptable to have it as a manual process. (i won't stand in the way if someone wants to automate it of course...)
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company