Updated Release Process (markdown)

Tom Wilkie
2015-09-04 10:46:45 +01:00
parent 6331e8f47c
commit ad7f9d0073
+2 -1
@@ -8,4 +8,5 @@ Other pointers:
- Release notes should only contain user visible changes; new features and bug fixes. Refactorings don't need to be documented.
- Useful when compiling release notes is the [changes since last release](https://github.com/weaveworks/scope/compare/latest_release...master)
- Also note most pull requests have the issue number in the branch name, which is helpful
- *MAKE SURE* you update your ```make deps``` tools (for instance, ```docker-squash```) and go-gotten dependancies, so you're not compiling with an old version of some library.
- *MAKE SURE* you update your ```make deps``` tools (for instance, ```docker-squash```) and go-gotten dependancies, so you're not compiling with an old version of some library.
- Also, don't forget to do a ```make static```