Le 27/05/2010 17:30, Christopher Browne a écrit :
> Steve Singer wrote:
>> Guillaume Lelarge wrote:
>>
>> The 1.2 documentation is actually available at
>> http://lists.slony.info/adminguide/1.2/doc/adminguide/index.html there
>> is just no link to it from the main page.
>>
>> I've posted a version of that file (for discussion purposes, I have
>> not yet committed it to cvs) at  http://www.slony.info/versions.rss
>>
>> Should the <link> point at the documentation or the source tar?
>>
>> What are proper values of the guid?
>>
>> Do other people find this thing useful? We would have to manually
>> update it each time we do a release (which isn't a big deal if people
>> use it)
> 
> I'd be completely disinclined to create a manual update process for
> this; that's going to fall out of date and get forgotten quickly.  I
> think, however, it should be pretty possible to automate it.
> 
> Consider...
> 
> When tarballs are deployed, we already use a makefile to regenerate
> md5 checksums.
> 
> Each tarball does contain release notes, always stored in the file
> "RELEASE".
> 
> Perhaps the Makefile could be extended to pull release notes out of
> the tarballs, something like the following...
> 
>  For each tarball
> 
>    - Create a subdirectory based on version name
> 
>    - Untar the RELEASE file
> 
>    - Pull timestamp off the tarball, and generate an RSS entry
>      consisting of a reference to the release notes, a description
>      generated out of the release number, and the timestamp
> 
> The pieces then get assembled into an RSS file.
> 

It seems way better to me. I'm all for automatic maintenance of this kind :)


-- 
Guillaume
 http://www.postgresql.fr
 http://dalibo.com