From ad7f9d00739adef1d3b9dc41afacdd73852dc619 Mon Sep 17 00:00:00 2001 From: Tom Wilkie Date: Fri, 4 Sep 2015 10:46:45 +0100 Subject: [PATCH] Updated Release Process (markdown) --- Release-Process.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Release-Process.md b/Release-Process.md index f8d7339..b290c4d 100644 --- a/Release-Process.md +++ b/Release-Process.md @@ -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. \ No newline at end of file +- *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``` \ No newline at end of file