Consolidate repo graph by merging stale branches
- At the first glance the repository graph is quite confusing, I - as newbie to the repo - miss
- clear separation of integration branch and release branch, e.g.
master
andstable
- more obvious tagging concept
- feature branches merged back to master
- clear separation of integration branch and release branch, e.g.
- At the second glance the graph presents itself as quite straight-forward
- only
master
,revert-6f07de61
andFEATURE-reconfigured_import_users_access
seems separate branches Is this really correct? - In my view, there is nothing against a merge of
FEATURE-reconfigured_import_users_access
tomaster
- only
Proposal
- Make component lifecycle more convention-compliant
- Merge feature branches to
master
- If really needed: Tag heads of stale branches with speaking names (e.g. branch names) and then remove branches
- Introduce
stable
branch and release process
- Merge feature branches to
Edited by Alexander Mühlbauer