Strategies
The table below provides a high-level comparison of the strategies for establishing new code repositories. Each strategy serves as a flexible blueprint and is discussed in more detail in the following sub-pages, allowing teams to adapt it to their workflows, processes, and release schedules.
Fundamental
Fast
High
Small development teams with minimal entrenched processes, low change volume, or infrequent releases. Suitable for teams that are tolerant of short-term disruption in exchange for a rapid transition.
Incremental
Medium
Low
Larger development teams without deeply entrenched tooling or processes. Suitable where a controlled transition is required, allowing developers to pilot new ways of working before full adoption.
Advanced
Slow
Low
Large development teams with tightly coupled or entrenched processes. Suitable where disruption must be minimised, pilot phases are essential, and there is a requirement to rebuild repositories from scratch without losing change history if issues are discovered.
These strategies are not rigid. Teams can tailor or combine approaches as needed to balance speed, risk, and operational impact, ensuring a safe and practical transition to JadeGit.
Last updated