diff options
| author | Nick Thomas <nick@gitlab.com> | 2016-10-02 12:32:30 +0100 |
|---|---|---|
| committer | Nick Thomas <nick@gitlab.com> | 2016-10-02 20:36:45 +0100 |
| commit | 267a96f3d42c1cdd38fc1424fe2e53ede8bd9950 (patch) | |
| tree | a94e57973987adab236b0e4e2543edee128e7ba0 | |
| parent | c9352aa6e388293784f50ecd26892f1780522256 (diff) | |
| download | gitlab-ce-267a96f3d42c1cdd38fc1424fe2e53ede8bd9950.tar.gz | |
Link to the "What requires downtime?" page from the Migration Style Guide
[ci skip]
| -rw-r--r-- | doc/development/migration_style_guide.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/development/migration_style_guide.md b/doc/development/migration_style_guide.md index 295eae0a88e..61b0fbc89c9 100644 --- a/doc/development/migration_style_guide.md +++ b/doc/development/migration_style_guide.md @@ -9,10 +9,10 @@ a big burden for most organizations. For this reason it is important that your migrations are written carefully, can be applied online and adhere to the style guide below. Migrations should not require GitLab installations to be taken offline unless -_absolutely_ necessary. If a migration requires downtime this should be -clearly mentioned during the review process as well as being documented in the -monthly release post. For more information see the "Downtime Tagging" section -below. +_absolutely_ necessary - see the ["What Requires Downtime?"](what_requires_downtime.md) +page. If a migration requires downtime, this should be clearly mentioned during +the review process, as well as being documented in the monthly release post. For +more information, see the "Downtime Tagging" section below. When writing your migrations, also consider that databases might have stale data or inconsistencies and guard for that. Try to make as little assumptions as possible |