@@ -158,14 +158,11 @@
158 * Run packcheck on the uploaded package. To get the latest uploaded
158 * Run packcheck on the uploaded package. To get the latest uploaded
159 version from hackage, run `cabal unpack <package-name>`. You might
159 version from hackage, run `cabal unpack <package-name>`. You might
160 have to run `cabal update`.
160 have to run `cabal update`.
161− * Create a git tag corresponding to the release where X.Y.Z is the new
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
162− package version (`git tag vX.Y.Z && git push -f origin vX.Y.Z`).
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
163 * Add to stackage (`build-constraints.yaml` in Stackage repo) if needed
165 * 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`)
169 * Update and if needed release streaming-benchmarks package
166 * Update and if needed release streaming-benchmarks package
170 * Check https://matrix.hackage.haskell.org/package/streamly
167 * Check https://matrix.hackage.haskell.org/package/streamly
171 * Check haddocks on Hackage, upload if not built
168 * Check haddocks on Hackage, upload if not built