for_developers:bugfixprocess
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
for_developers:bugfixprocess [2019/01/31 17:19] – Created kunz | for_developers:bugfixprocess [2020/06/26 14:36] – kunz | ||
---|---|---|---|
Line 65: | Line 65: | ||
< | < | ||
git add *CHANGELOG.md* | git add *CHANGELOG.md* | ||
- | git commit -m "Bug Fix Release v1.0.0" | + | git commit -m "Bug Fix Release v1.0.1" |
git push | git push | ||
</ | </ | ||
Line 80: | Line 80: | ||
It is very important, that the right release branch is selected. The form must be completed as shown in the picture below. | It is very important, that the right release branch is selected. The form must be completed as shown in the picture below. | ||
- | {{: | + | {{: |
Note that the information in the description section is copied from the change log. | Note that the information in the description section is copied from the change log. | ||
Line 87: | Line 87: | ||
==== 7. Merge the bug fix into the newer release branches | ==== 7. Merge the bug fix into the newer release branches | ||
- | The bug fix must be applied on all newer releases too. Therefore, the bug fix must be merged upwards through all releases (merge cascade). After each merge, the change log is updated on the corresponding release branch and a release tag created. Basically, the steps 5 and 6 must be executed. | + | The bug fix must be applied on all newer releases |
The following git commands show the procedure for one cascade. It must be repeated. | The following git commands show the procedure for one cascade. It must be repeated. |
for_developers/bugfixprocess.txt · Last modified: 2020/06/26 14:52 by kunz