From 6331e8f47cc1caa393af60738742bb23ae648608 Mon Sep 17 00:00:00 2001 From: Tom Wilkie Date: Fri, 4 Sep 2015 10:22:19 +0100 Subject: [PATCH] Updated Release Process (markdown) --- Release-Process.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/Release-Process.md b/Release-Process.md index d6edc7c..f8d7339 100644 --- a/Release-Process.md +++ b/Release-Process.md @@ -2,4 +2,10 @@ We use the same script as Weave, hence the same documentation applies. * https://github.com/weaveworks/weave/wiki/Release-Process -*BEWARE* when copying `git push -f git@github.com:weaveworks/weave latest_release v0.7.1`, you're pushing to the weave repo. It should be `git push -f git@github.com:weaveworks/scope latest_release v0.7.1`. \ No newline at end of file +*BEWARE* when copying `git push -f git@github.com:weaveworks/weave latest_release v0.7.1`, you're pushing to the weave repo. It should be `git push -f git@github.com:weaveworks/scope latest_release v0.7.1`. + +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