@@ -112,7 +112,7 @@ main = withSocketsDo . bracket (forkIO startServer) killThread $ \_threadid -> d
113If you run this, you should get:
113If you run this, you should get:
116$ cabal new-build cookbook-file-upload
116$ cabal new-build cookbook-file-upload
118$ dist-newstyle/build/x86_64-linux/ghc-8.2.1/cookbook-file-upload-0.1/x/cookbook-file-upload/build/cookbook-file-upload/cookbook-file-upload
118$ dist-newstyle/build/x86_64-linux/ghc-8.2.1/cookbook-file-upload-0.1/x/cookbook-file-upload/build/cookbook-file-upload/cookbook-file-upload
@@ -131,55 +131,8 @@ introduces the core features of servant. After this article, you should be able
131to write your first servant webservices, learning the rest from the haddocks'
131to write your first servant webservices, learning the rest from the haddocks'
134−The central documentation can be found [here](http://haskell-servant.readthedocs.org/).
134+[...]
135−Other blog posts, videos and slides can be found on the
135+
136−[website](http://haskell-servant.github.io/).
138−If you need help, drop by the IRC channel (#servant on freenode) or [mailing
139−list](https://groups.google.com/forum/#!forum/haskell-servant).
143−This table lists the versions of some `servant-` libraries at the point of
144−release of `servant` package.
146−| | **0.10** | **0.11** | **0.12** |
147−| ------------------- | -------- |----------|----------|
148−| servant | 0.10 | 0.11 | 0.12 |
149−| servant-blaze | 0.7.1 | ? | ? |
150−| servant-cassava | 0.7 | ? | ? |
151−| servant-client | 0.10 | 0.11 | 0.12 |
152−| servant-docs | 0.10 | 0.11 | 0.11.1 |
153−| servant-foreign | 0.10 | 0.10.0.1 | 0.10.2 |
154−| servant-js | 0.9.1 | ? | ? |
155−| servant-lucid | 0.7.1 | ? | ? |
156−| servant-mock | 0.8.1.1 | ? | ? |
157−| servant-server | 0.10 | 0.11 | 0.12 |
158−| servant-swagger | 1.1.2.1 | ? | ? |
162−See `CONTRIBUTING.md`
164−## Release process outline (by phadej)
166−- Update changelog and bump versions in `master`
167− - `git log --oneline v0.12.. | grep 'Merge pull request'` is a good starting point (use correct previous release tag)
168−- Create a release branch, e.g. `release-0.13`, and *protect it* from accidental force pushes.
169− - Release branch is useful for backporting fixes from `master`
170−- Smoke test in [`servant-universe`](https://github.com/phadej/servant-universe)
171− - `git submodule foreach git checkout master` and `git submodule foreach git pull` to get newest of everything.
172− - `cabal new-build --enable-tests all` to verify that everything builds, and `cabal new-test all` to run tests
173− - It's a good idea to separate these steps, as tests often pass, if they compile :)
174− - See `cabal.project` to selectively `allow-newer`
175− - If some packages are broken, on your discretisation there are two options:
176− - Fix them and make PRs: it's good idea to test against older `servant` version too.
177− - Temporarily comment out broken package
178− - If you make a commit for `servant-universe`, you can use it as submodule in private projects to test even more
179−- When ripples are cleared out:
180− - `git tag -s` the release
182− - `cabal sdist` and `cabal upload`
183Response {responseStatus = Status {statusCode = 200, statusMessage = "OK"}, responseVersion = HTTP/1.1, responseHeaders = [("Transfer-Encoding","chunked"),("Date","Fri, 08 Dec 2017 16:50:14 GMT"),("Server","Warp/3.2.13"),("Content-Type","application/json;charset=utf-8")], responseBody = "0", responseCookieJar = CJ {expose = []}, responseClose' = ResponseClose}
136Response {responseStatus = Status {statusCode = 200, statusMessage = "OK"}, responseVersion = HTTP/1.1, responseHeaders = [("Transfer-Encoding","chunked"),("Date","Fri, 08 Dec 2017 16:50:14 GMT"),("Server","Warp/3.2.13"),("Content-Type","application/json;charset=utf-8")], responseBody = "0", responseCookieJar = CJ {expose = []}, responseClose' = ResponseClose}