Ah, please don't add stuff to the top of `CHANGES.markdown` -- it screws up my automated scripts for making minor (bug fix-level) releases, causes merge conflicts with the stable release branch, etc.  Perhaps instead we should make a file called `CHANGES-HEAD.markdown` or something like that, which can be added to the top of `CHANGES.markdown` when the time comes to make a new feature release?