Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
aa82887f
Commit
aa82887f
authored
Dec 02, 2020
by
Alex Ives
Committed by
Mayra Cabrera
Dec 02, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Change remove_after in what requires downtime docs
Relates to
https://gitlab.com/gitlab-org/gitlab/issues/290244
parent
9428bed1
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
doc/development/what_requires_downtime.md
doc/development/what_requires_downtime.md
+1
-1
No files found.
doc/development/what_requires_downtime.md
View file @
aa82887f
...
...
@@ -51,7 +51,7 @@ We require indication of when it is safe to remove the column ignore with:
-
`remove_with`
: set to a GitLab release typically two releases (M+2) after adding the
column ignore.
-
`remove_after`
: set to a date after which we consider it safe to remove the column
ignore, typically
last date of the development cycle of release M+2 - namely the release dat
e.
ignore, typically
after the M+1 release date, during the M+2 development cycl
e.
This information allows us to reason better about column ignores and makes sure we
don't remove column ignores too early for both regular releases and deployments to GitLab.com. For
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment