diff options
author | Yorick Peterse <yorickpeterse@gmail.com> | 2017-08-04 14:30:57 +0300 |
---|---|---|
committer | Yorick Peterse <yorickpeterse@gmail.com> | 2017-08-04 14:34:42 +0300 |
commit | d5cb29434a375bbbe10c4aa016bf6631bf8ede6c (patch) | |
tree | e6e9529420915a069a27da8ead73ccb94721f68a /doc/development/migration_style_guide.md | |
parent | 9d3f27a22d0193de15cb40e5cab1c437c61eca69 (diff) |
Mention schema migrations and patch releases
Diffstat (limited to 'doc/development/migration_style_guide.md')
-rw-r--r-- | doc/development/migration_style_guide.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/development/migration_style_guide.md b/doc/development/migration_style_guide.md index 5aac243ae3d..9b8ab5da74e 100644 --- a/doc/development/migration_style_guide.md +++ b/doc/development/migration_style_guide.md @@ -35,6 +35,12 @@ Please don't depend on GitLab-specific code since it can change in future versions. If needed copy-paste GitLab code into the migration to make it forward compatible. +## Schema Changes + +Migrations that make changes to the database schema (e.g. adding a column) can +only be added in the monthly release, patch releases may only contain data +migrations _unless_ schema changes are absolutely required to solve a problem. + ## Downtime Tagging Every migration must specify if it requires downtime or not, and if it should |