Good news. It would be nice to have most major bugs cleaned out, so we can manage to test those victory conditions properly before 0.8.
On a separate note, I saw you had a request that bugs should not be reported as fixed in 0.75b. Does that count for 0.75c as well (and other dev releases)? Should all bug fixes be always marked as resolved in 0.next, for a clear Changelog between two official releases? - EDIT: Seeing how you marked all your fixes before and after 0.75c, I have my answer already. I’ll move the 2 reports marked as fixed for 0.75c to 0.next.
I want to use automatically generated changelog for 0.8 public release. Thus reports should be marked as fixed in 0.next (which will be renamed to 0.8) only if issue was present in 0.75 release.
If issue showed later (in one of recent dev releases), it should be marked as fixed in “next dev release” or simply left the field empty. I don’t know if there is a point in having listed in changelog ephemeral regressions that wasn’t present in any “official” (not dev) release.
Not sure if it’s a good idea, but perhaps we could have another version code “0.dev”, to be used only for bugs reported on dev versions, related to the changes in that version (i.e.: sth related to the new Kingdom Overview would be 0.dev, while a typo in a skill description, which probably was there before, could be 0.next). Though perhaps this may become too cumbersome for the devs.