User Tools

Site Tools


for_developers:releaseprocess

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
for_developers:releaseprocess [2019/01/30 10:57]
kunz Improve chapter 6 & 8
for_developers:releaseprocess [2019/01/31 16:46] (current)
kunz Fix typo
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 //​MAJOR.MINOR//​ part of the release number. Only the release tags contain the full pattern. 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 //​MAJOR.MINOR//​ part of the release number. Only the release tags contain the full pattern.
  
-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):
  
 <​code>​ <​code>​
for_developers/releaseprocess.1548842272.txt.gz · Last modified: 2019/01/30 10:57 by kunz