Open-Harbor/osrm-backend
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 3 Wiki Activity

[skip ci] clarify release branches

Browse Source
This commit is contained in:
Patrick Niklaus 2016-11-14 23:21:19 +00:00
parent 7e4020c010
commit 3235f30a98
No known key found for this signature in database
GPG Key ID: E426891B5F978B1B
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/releasing.md
View File

@ -32,6 +32,7 @@ We may introduce forward-compatible changes: query parameters and response prope
- The `master` branch is for the bleeding edge development - The `master` branch is for the bleeding edge development
- We create and maintain release branches `x.y` to control the release flow - We create and maintain release branches `x.y` to control the release flow
- We create the release branch once we tagged the final version `x.y.0` version, RCs go on master
- No minor or major version will be released without a code-equal release candidates - No minor or major version will be released without a code-equal release candidates
- For quality assurance, release candidates will be run on the demo server for 24 hours before releaseing the version proper - For quality assurance, release candidates will be run on the demo server for 24 hours before releaseing the version proper
- Patch versions may be released without a release candidate - Patch versions may be released without a release candidate