Changes for page Development in branches
Last modified by Alexander Schulz-Rosengarten on 2023/09/05 10:52
<
edited by Alexander Schulz-Rosengarten
on 2023/07/11 10:32
on 2023/07/11 10:32
edited by Alexander Schulz-Rosengarten
on 2023/09/05 10:52
on 2023/09/05 10:52
Change comment:
Renamed back-links.
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,1 +1,1 @@ 1 -K ieler.Development.Guidelines.Using Git.WebHome1 +KIELER.Development.Guidelines.Using Git.WebHome - Content
-
... ... @@ -2,13 +2,13 @@ 2 2 3 3 == Branches? == 4 4 5 -Yes, branches! This shows the KIELER branching scheme. If you want to know whatever the different classes of branches do, check [[doc:K ieler.Processes.Source Code Management.WebHome]].5 +Yes, branches! This shows the KIELER branching scheme. If you want to know whatever the different classes of branches do, check [[doc:KIELER.Development.Processes.Source Code Management.WebHome]]. 6 6 7 7 [[image:attach:branches.png]] 8 8 9 9 == Why and how to use branches == 10 10 11 -Now you should now which use the different kinds of branches have, if not, go back to [[doc:K ieler.Processes.Source Code Management.WebHome]].11 +Now you should now which use the different kinds of branches have, if not, go back to [[doc:KIELER.Development.Processes.Source Code Management.WebHome]]. 12 12 13 13 Ok, now nearly everything should be clear. We want to implement everything in features. The master branch should always be release-ready. For developers this means: 14 14