summaryrefslogtreecommitdiff
path: root/RELEASE.md
diff options
context:
space:
mode:
authorkrangelov <kr.angelov@gmail.com>2021-09-22 14:11:27 +0200
committerkrangelov <kr.angelov@gmail.com>2021-09-22 14:11:27 +0200
commite4b2f281d97f97317df37b5e296cea371c334f37 (patch)
tree8fa7f7a4b47a85f6269f4a734cb8414dccde60f5 /RELEASE.md
parent063c517f3c99aa34ebf5ce25a97d85bb05d7abe4 (diff)
parentbedb46527daa99125f103b87e9fdf8e3cbe9d98b (diff)
Merge branch 'master' of github.com:GrammaticalFramework/gf-core
Diffstat (limited to 'RELEASE.md')
-rw-r--r--RELEASE.md11
1 files changed, 7 insertions, 4 deletions
diff --git a/RELEASE.md b/RELEASE.md
index 04bd4b933..1deaa3a90 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -47,11 +47,14 @@ but the generated _artifacts_ must be manually attached to the release as _asset
In order to do this you will need to be added the [GF maintainers](https://hackage.haskell.org/package/gf/maintainers/) on Hackage.
-1. Run `make sdist`
+1. Run `stack sdist --test-tarball` and address any issues.
2. Upload the package, either:
- 1. **Manually**: visit <https://hackage.haskell.org/upload> and upload the file `dist/gf-X.Y.tar.gz`
- 2. **via Cabal (≥2.4)**: `cabal upload dist/gf-X.Y.tar.gz`
-3. If the documentation-building fails on the Hackage server, do:
+ 1. **Manually**: visit <https://hackage.haskell.org/upload> and upload the file generated by the previous command.
+ 2. **via Stack**: `stack upload . --candidate`
+3. After testing the candidate, publish it:
+ 1. **Manually**: visit <https://hackage.haskell.org/package/gf-X.Y.Z/candidate/publish>
+ 1. **via Stack**: `stack upload .`
+4. If the documentation-building fails on the Hackage server, do:
```
cabal v2-haddock --builddir=dist/docs --haddock-for-hackage --enable-doc
cabal upload --documentation dist/docs/*-docs.tar.gz