@@ -19,18 +19,12 @@
1919 * Make sure the description in cabal file is in sync with README and other docs
2020 * Make sure CI configs include last three major releases of GHC in CI testing.
2121 * Update `tested-with` field
22− * Make sure all dependency bounds are correct
22+ * Make sure all dependency bounds can use latest versions
2323
2424* _Update changelog & Version_:
2525
2626 * Change the `Unreleased` section at the top of changelog file to the new
27− release version number. Using `Unreleased` instead of the next release
28− number for unreleased changes is important. First, we do not know the
29− next release number in advance, it could be a major or minor release.
30− Second, if we use the next release number instead, then when adding a new
31− change to the changelog, at one look we cannot know whether the release
32− number on top is unreleased or released.
33−
27+ release version number.
3428 * Make sure all the bug fixes being included in this release are marked
3529 with a target release on github. So that users can search by release if
3630 they want.
@@ -90,6 +84,15 @@ following:
9084* wontfix
9185* maintenance
9286
87+### Changelog Management
88+
89+Keep the unreleased changes in the `Unreleased` section at the top of changelog
90+file. Using `Unreleased` instead of the next release number for unreleased
91+changes is important. First, we do not know the next release number in advance,
92+it could be a major or minor release. Second, if we use the next release
93+number instead, then when adding a new change to the changelog, at one look we
94+cannot know whether the release number on top is unreleased or released.
95+
9396## TODO
9497
9598* GPG signed releases and tags