for_developers:releaseprocess
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
for_developers:releaseprocess [2019/01/30 10:57] – Improve chapter 6 & 8 kunz | for_developers:releaseprocess [2019/01/31 16:46] – Fix typo kunz | ||
---|---|---|---|
Line 35: | Line 35: | ||
The EEROS release workflow supports multiple active releases. Therefore, every release is created on a release branch. The name of the release branch contains the // | The EEROS release workflow supports multiple active releases. Therefore, every release is created on a release branch. The name of the release branch contains the // | ||
- | Since the development is done on the master branch, the release branch is created based on the HEAD of the master branch. The following git commands will create the new release branch (release/1.0 is used as an example): | + | Since the development is done on the master branch, the release branch is created based on the HEAD of the master branch. The following git commands will create the new release branch (v1.0 is used as an example): |
< | < |
for_developers/releaseprocess.txt · Last modified: 2023/12/16 10:50 by ursgraf