on master help sign in
Shift the order of tasks in the release checklist

Create a version tag once the candidate is verified and the package in uploaded.

commit6e898cde23347618865cc37bd3d623a1f51a1939 authorAdithya Kumar <adithya@composewell.com> dateThu 3 Mar 2022, 00:00 (5 years ago) parent956faed
1 file changed+2−2
dev/MAINTAINING.md+2−2
dev/MAINTAINING.md+2−2
@@ -137,8 +137,6 @@
137137
138138 * Wait for final CI tests to pass:
139139
140− * Create a git tag corresponding to the release where X.Y.Z is the new
141− package version (`git tag vX.Y.Z && git push -f origin vX.Y.Z`).
142140 * Mask out the build status lines from the
143141 [docs/Introduction.md](/docs/Introduction.md)
144142 * Upload to hackage
@@ -156,6 +154,8 @@
156154 * Run packcheck on the uploaded package. To get the latest uploaded
157155 version from hackage, run `cabal unpack <package-name>`. You might
158156 have to run `cabal update`.
157+ * Create a git tag corresponding to the release where X.Y.Z is the new
158+ package version (`git tag vX.Y.Z && git push -f origin vX.Y.Z`).
159159 * Add to stackage (`build-constraints.yaml` in Stackage repo) if needed
160160 * Optionally upload `package-X.Y.Z-sdist.tar.gz` to github release page
161161 * Update release contributors on github release page