[tei-council] New document describing release steps
Martin Holmes
mholmes at uvic.ca
Fri Feb 3 08:30:35 EST 2012
I agree; I think only a human can determine which SVN changes deserve
mention in the release notes and which don't. Unless, of course, we
adopt a rigorous convention for SVN commit messages that would enable
them to be processed mechanically. But that seems far-fetched.
That "XML 101, Martin..." message is going to haunt me for ever. :-)
Cheers,
Martin
On 12-02-03 05:20 AM, Lou Burnard wrote:
> On 03/02/12 13:11, Sebastian Rahtz wrote:
>> some notes on http://www.tei-c.org/Activities/Council/Working/tcw22.xml
>>
>> 1) the command "make changelog" in the P5 sources remakes the file ReleaseNotes/ChangeLog which contains a human-readable summary of changes from SVN. I am wondering how to automate this
>>
>
> It's also perhaps worth noting somewhere that the ChangeLog isnot the
> same as the human-readable readme files included in the release. I have
> always hand-crafted the former from the latter and I don't see any
> obvious way of automating that process.
>
More information about the tei-council
mailing list