Development model is "Single Repo"
- Acronym
- single-repo-development
- Belongs to
- SIG DevOps
- Responsible
- SohleDelfin6504 und Stefan Bente
- History
- (v1) 2021-01-15 - created initially
- (v2) 2021-01-22 - scope enhanced (includes also branching rules)
- (v3) 2021-01-22 - updated the deadline
- (v4) 2021-01-23 - decide decision
- (v5) 2021-01-29 - done todos
- (v6) 2021-02-19 - rename decision
- (v7) 2021-02-19 - corrected text
Why is there need for such a decision?
This decision is important, because it will decide how the project will store in git.
Viable Options
- single repo
- one repo for every sub-domain (multi-repo)
How is this decision evaluated?
The decision is based on a history of the project structure.
Resolution Details
There will be one repo for the whole project at git.
Reasons for the resolution
To understand this decision it is good to know the project structure project structure with his history. The fact that there is only one src folder with domain packages eliminates the need for a multi-repo.