On Wednesday 26 September 2007 10:10, Martijn Faassen wrote:
> This way checking CHANGES.txt should tell you what's going on with
> releases. If someone forgot to do the last step, you see immediately
> something is wrong, as you want to add your change to the 'unreleased'
> section but there's nothing there yet. You can then reconstruct what
> happened from the cheeseshop or the tags, and put in a new 'unreleased'
Good point; of course I agree. :-) A well-maintained CHANGES.txt file is worth
CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training
Zope3-dev mailing list