Merge pull request #293 from carlaKC/inrepo-releasenotes

mutli: add release notes file to track in-repo

.github/pull_request_template.md

@@ -0,0 +1,2 @@
+#### Pull Request Checklist
+- [ ] Update `release_notes.md` if your PR contains major features, breaking changes or bugfixes

release_notes.md

@@ -0,0 +1,18 @@
+# Loop Client Release Notes
+This file tracks release notes for the loop client. 
+
+### Developers: 
+* When new features are added to the repo, a short description of the feature should be added under the "Next Release" heading.
+* This should be done in the same PR as the change so that our release notes stay in sync!
+
+### Release Manager: 
+* All of the items under the "Next Release" heading should be included in the release notes.
+* As part of the PR that bumps the client version, the "Next Release" heading should be replaced with the release version including the changes.
+
+## Next Release
+
+#### New Features
+
+#### Breaking Changes
+
+#### Bug Fixes

version.go

@@ -21,6 +21,7 @@ const semanticAlphabet = "0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqr
 // These constants define the application version and follow the semantic
 // versioning 2.0.0 spec (http://semver.org/).
 const (
+	// Note: please update release_notes.md when you change these values.
 	appMajor uint = 0
 	appMinor uint = 9
 	appPatch uint = 0