Browse Source

Merge pull request #293 from carlaKC/inrepo-releasenotes

mutli: add release notes file to track in-repo
pull/294/head
Carla Kirk-Cohen 1 month ago
committed by GitHub
parent
commit
ccb9e077d7
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 21 additions and 0 deletions
  1. +2
    -0
      .github/pull_request_template.md
  2. +18
    -0
      release_notes.md
  3. +1
    -0
      version.go

+ 2
- 0
.github/pull_request_template.md View File

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

+ 18
- 0
release_notes.md View File

@ -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

+ 1
- 0
version.go View File

@ -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

Loading…
Cancel
Save