Differences

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

--- for_developers:releaseprocess [2019/01/25 14:35] – update a few chapters 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 //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>
@@ Line 97: / Line 97: @@
 It is very important, that the right release branch is selected. The form must be completed as shown in the picture below.
-//insert picture//
+{{:for_developers:release_v1.0.0_github_1.png?nolink|}}
+Note that the information in the description section is copied from the change log.
@@ Line 130: / Line 132: @@
 </code>
-The documentation is found at the path //eeros-framework/buildFolder/doc/html//. The HTML documentation is uploaded as described below:
+The documentation is found at the path **eeros-framework/buildFolder/doc/html**. It is uploaded by the administrator of the EEROS Website. He must be contacted using the [[http://eeros.org/wordpress/contact/|contact form]]. Afterwards, he will answer with the procedure to hand over the files.
-//describe upload.//
 ==== 9. Creation of a new card to discuss suggestions for improvement  ====