for_developers:releaseprocess
                Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| for_developers:releaseprocess [2019/03/28 16:19] – [8. Generate the API documentation with Doxygen] graf | for_developers:releaseprocess [2024/12/18 11:33] (current) – [2. Creation of a new release branch] ursgraf | ||
|---|---|---|---|
| Line 45: | Line 45: | ||
| < | < | ||
| git push --set-upstream origin v1.0 | git push --set-upstream origin v1.0 | ||
| + | </ | ||
| + | |||
| + | Probably you already have a release branch, e.g. do want to release v1.0.3 and still have your branch for v.1.0.2. If so, switch to branch v1.0 and **merge your master branch** (or whatever work you want to be included) into the release branch. | ||
| + | < | ||
| + | git checkout v1.0 | ||
| + | git merge master | ||
| </ | </ | ||
| Line 122: | Line 128: | ||
| The change is committed and pushed. | The change is committed and pushed. | ||
| + | < | ||
| + | git add *CHANGELOG.md* | ||
| + | git commit -m "Add unreleased section" | ||
| + | git push | ||
| + | </ | ||
| ==== 8. Generate the API documentation with Doxygen | ==== 8. Generate the API documentation with Doxygen | ||
| - | The second last step is to update the [[http:// | + | The second last step is to update the [[http:// | 
| < | < | ||
for_developers/releaseprocess.1553786346.txt.gz · Last modified: 2019/03/28 16:19 by graf
                
                