diff options
| author | Andrew Newdigate <andrew@gitlab.com> | 2017-07-06 14:52:54 +0300 |
|---|---|---|
| committer | Andrew Newdigate <andrew@gitlab.com> | 2017-07-06 14:52:54 +0300 |
| commit | 106e3c65d5f8d45a5ec79be770983aedccd4bd88 (patch) | |
| tree | e4bd2f588e507885a5979306160a3298fb4326ce | |
| parent | 729bb377b92aea76a2f35cbfb91ccb3c267e5972 (diff) | |
| parent | b006bfdb3619249a7ea01d1e3fbe6dc409730ec6 (diff) | |
Merge branch 'migration-process-updates' into 'master'
Update the migration process as per retrospective
See merge request !165
| -rw-r--r-- | doc/MIGRATION_PROCESS.md | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/MIGRATION_PROCESS.md b/doc/MIGRATION_PROCESS.md index 268fade8d..d512e067f 100644 --- a/doc/MIGRATION_PROCESS.md +++ b/doc/MIGRATION_PROCESS.md @@ -28,6 +28,14 @@ The order of migration is roughly determined using the formula described in the Once a route has been selected, the route in the client will be analysed and profiled in order to figure out the best way of migrating the route to Gitaly. +During the migration analysis, the following factors should be taken into consideration: + +1. *Test coverage of the legacy code*: + * How well covered is the legacy code? Use https://gitlab-org.gitlab.io/gitlab-ce/coverage-ruby to find out. + * Are there important codepaths in the legacy code base that are not being tested? + * If so, should we create tests for these codepaths before continuing with the migration? +1. + The artefacts of this stage will be: 1. **Rough estimation of the amount of work involved in the migration**: from the analysis, we should have a rough idea of how long this migration will take. |