@@ -13,19 +13,6 @@
1313 * Check regressions from previous release
1414 * Check comparative benchmarks using streaming-benchmarks
1515
16−* _Update changelog_:
17−
18− * Change the `Unreleased` section at the top of changelog file to the new
19− release version number and make an `Unreleased` section above it. Using
20− `Unreleased` instead of the next release number for unreleased changes is
21− important. If we use the next release number instead, then when adding a
22− new change to the changelog, at one look we cannot know whether the
23− release number on top is unreleased or released.
24−
25− * Make sure all the bug fixes being included in this release are marked
26− with a target release on github. So that users can search by release if
27− they want.
28−
2916* _Update Package Metadata:_
3017
3118 * Update `stack.yaml` to latest stable resolver, cleanup extra-deps
@@ -33,6 +20,20 @@
3320 * Make sure CI configs include last three major releases of GHC in CI testing.
3421 * Update `tested-with` field
3522 * Make sure all dependency bounds are correct
23+
24+* _Update changelog & Version_:
25+
26+ * 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+
34+ * Make sure all the bug fixes being included in this release are marked
35+ with a target release on github. So that users can search by release if
36+ they want.
3637 * Bump the package version
3738
3839* _Upload_: