> On Sat, Jun 14, 2008 at 2:25 AM, Magnus Hagander <magnus@hagander.net> wrote:
>>
>> What would be cool is if it could track the version RSS feed from
>> www.postgresql.org to figure out when it needs to go out and check the
>> others...
>>
>
> Well, which one is most likely to be correct? If the RSS feed needs to
> be updated manually after the new release is added to the FTP site,
> maybe it would make more sense to add the RSS to the list of "pages"
> to verify for up-to-dateness. The primary source of information should
> be correct by default (which is why I'm looking at FTP directory
> names--assuming the release exists iff you can download the source
> code).
The RSS feed is the definitive source. We preload binaries and source
tarballs onto the ftp site a few days before the release, so we don't
want your script bugging us prior to the actual launch otherwise it'll
end up getting forgotten. The data source for the RSS feed is one of
the things that gets updated *at* release time.
Oh, and I would suggest running it daily. If the folks updating the
sites cannot handle same-day updates, or on the odd occasion ignoring
a couple of emails until they can do the update, then they're probably
not the most appropriate people for handling this kind of task anyway.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-advocacy mailing list (pgsql-advocacy@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-advocacy
No comments:
Post a Comment