Incorrect version in released changelogs #12
Description
The last several releases by BINARY have had the wrong (non-incremented) version on the latest entry in the changelog, in the released tarball. I believe this is because in dist.ini, [NextRelease] is executed before [ReversionOnRelease]. This means that [NextRelease] will insert the old version before [ReversionOnRelease] increments it. (The Changes file in the repository is then updated after release, when the version number has already been updated regardless.) This can be fixed by moving [NextRelease] after [ReversionOnRelease].