Re: CVS ChangeLog

On Wed, 30 Mar 2005, Steven Armstrong wrote:
>
> I was just preparing for tagging the current CVS state as version 1.2 
> when I noticed that the /pyblosxom/ChangeLog is way out of date.

The ChangeLog was totally different from what you just changed.  It was 
way out of date (we didn't use it anymore), but it contained a higher 
level revision history of what was going on with the code than the checkin 
comments for all checkins since the project started.


> google, once again beeing my friend, led me to a perl script [1] that
> generates the thing automatically from CVS checkin comments.

I've been using cvs2cl for a while now to figure out what changed between 
PyBlosxom versions.  It's a good tool.


> If you guys also thing that's a good idea I'll add that script to the 
> repo (e.g. to /pyblosxom/tools/) so we can just run that before any 
> future releases to update our ChangeLog.

I don't think this is necessary.  If we were better about the quality of 
our checkin comments and explaining what the ramifications of the changes 
were, then this would be useful.  But our checkin comments are pretty 
mediocre and I think they're only useful to us.


> There are also scripts and XSL stylesheets to generate HTML versions and 
> RSS feeds from it. Maybe that could be of use for pyblosxom.sf.net?

Mmm...  We already have a checkins mailing list.  I'm not sure posting it 
on the web-site (mostly updating the web-site constantly) and doing RSS 
feeds really helps us.


> Somehow related to this a question: Does the sourceforge cvs allow 
> custom scripts to be executed oncommit?

That's how the checkins mailing list works.

/will


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click