Establish migration approach flowchart
Overview
Need to determine how standard SVN repositories are structured to build a flowchart for how we perform migration. We're not going to be able to support every little nuance on how the SVN repo is structured. First we should start with the base case on how SVN projects are supposed to be organized:
In
For non standard cases like
Open questions
- Need to account for non-standardized filesystem organization - top level is organized into teams, for example.
- Can we use the atlassian tool shown above?
Tasks
-
Build a mapping doc that can be edited to cover mapping SVN concepts into git concepts. This should be human modify-able to be flexible during migration execution.
Acceptance Criteria
-
Update docs if needed
Edited by Bryan May