github/weave-scope
1
0
Fork 0
mirror of https://github.com/weaveworks/scope.git synced 2026-08-19 20:36:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Release Process (markdown)

Tom Wilkie
2015-09-04 10:22:19 +01:00
parent a58a4e809d
commit 6331e8f47c
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Release-Process.md
+7 -1
@@ -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`.
*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.