-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe how to release new version. #223
Conversation
README.md
Outdated
|
||
To release new version of marathon-consul follow steps: | ||
|
||
1. Commit all chagnes you need for release to master branch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
chagnes -> changes
README.md
Outdated
5. `make version v=<version>` e.g., `make version v=1.3.1` | ||
6. `git push` | ||
7. Create pull request from branch `release/<version>` to master. | ||
8. Once pull request get merged put tag on this commit (remember to update your master with `git pull`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
get -> gets
README.md
Outdated
8. Once pull request get merged put tag on this commit (remember to update your master with `git pull`) | ||
`git tag <version> -f` e.g., `git tag 1.3.1 -f`. Create annotated tag with release notes in it. | ||
9. Travis will automatically prepare github release from tag on master. Go there and update release notes. | ||
10. Copy github release to bintray. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a manual step?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. We can configure travis to release to bintray but we need to put company keys in configuration #180
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can keep copy scrip in repo so it will be easier to understand how to do it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK thx.
Refs: #221