Prepare 0.10.0 Release (#520)

- Update Changelog - Provide instructions for performing a release
improbable-eng · Aug 5, 2019 · 5096b58 · 5096b58
1 parent cf7d15a
commit 5096b58
Show file tree

Hide file tree

Showing 2 changed files with 18 additions and 1 deletion.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,3 +1,13 @@
+## 0.10.0
+### Breaking Changes
+* Server: Check flusher interface before calling Flush. [@mangas](https://github.com/mangas) in [#479](https://github.com/improbable-eng/grpc-web/pull/479)
+* Server: Remove `CloseNotify`. [@mangas](https://github.com/mangas) in [#478](https://github.com/improbable-eng/grpc-web/pull/478)
+* Client: Set Content-Length header in NodeHTTPTransport to disable chunked encoding. [@MichaelAquilina](https://github.com/MichaelAquilina) in [#427](https://github.com/improbable-eng/grpc-web/pull/427)
+* Server: Update grpc-go, golang/protobuf dependencies. [@johanbrandhorst](https://github.com/johanbrandhorst) in [#395](https://github.com/improbable-eng/grpc-web/pull/395)
+
+### Other Changes
+* Server: Add `grpc-status` & `grpc-message` as exposed headers. [@Globegitter](https://github.com/Globegitter) in [#489](https://github.com/improbable-eng/grpc-web/pull/489)
+
 ## 0.9.6
 ### Other Changes
 * Server: Allow non root resources. [@mangas](https://github.com/mangas) in [#454](https://github.com/improbable-eng/grpc-web/pull/454)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -68,4 +68,11 @@ At some point during the test run, execution will pause and the following line w
 INFO [karma]: Karma v3.0.0 server started at https://0.0.0.0:9876/
 ```
 
-This is your prompt to open a web browser on https://localhost:9876 at which point the tests will continue to run.
+This is your prompt to open a web browser on https://localhost:9876 at which point the tests will continue to run.
+
+## Creating a Release
+1. From a fresh checkout of master, create a release branch, ie: `feature/prepare-x.y.z-release`
+2. Update `CHANGELOG.md` by comparing commits to master since the last Github Release
+3. Raise a pull request for your changes, have it reviewed and landed into master.
+4. Switch your local checkout back to the master branch, pull your merged changes and run `./publish-release.sh`.
+5. Create the ARM binaries and attach them to the Github release.