on master help sign in
Update the MAINTAINING guide
commitc8e125f257b42ce2f806b756d2ab77b0bafcf2b0 authorAdithya Kumar <adithya@composewell.com> dateMon 13 Mar 2023, 20:13 (4 years ago) parent29b6293
1 file changed+4−7
docs/Developer/MAINTAINING.md+4−7
docs/Developer/MAINTAINING.md+4−7
@@ -158,14 +158,11 @@
158158 * Run packcheck on the uploaded package. To get the latest uploaded
159159 version from hackage, run `cabal unpack <package-name>`. You might
160160 have to run `cabal update`.
161− * Create a git tag corresponding to the release where X.Y.Z is the new
162− package version (`git tag vX.Y.Z && git push -f origin vX.Y.Z`).
161+ * Create a git tag of the form P-X.Y.Z corresponding to the release
162+ where X.Y.Z is the new package version and P is the package name (`git
163+ tag P-X.Y.Z && git push -f origin P-X.Y.Z`). If the package name is
164+ implicit, P can be omitted and the tag can be of the form vX.Y.Z
163165 * Add to stackage (`build-constraints.yaml` in Stackage repo) if needed
164− * Optionally upload `package-X.Y.Z-sdist.tar.gz` to github release page
165− * `gh release create vX.Y.Z --title "vX.Y.Z"`
166− * `gh release upload vX.Y.Z package-X.Y.Z-sdist.tar.gz`
167− * Update release contributors on github release page
168− (`git shortlog -s prev_tag..new_tag | sed $'s/^[0-9 \t]*/* /' | sort -f`)
169166 * Update and if needed release streaming-benchmarks package
170167 * Check https://matrix.hackage.haskell.org/package/streamly
171168 * Check haddocks on Hackage, upload if not built