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
35ff10f7
Commit
35ff10f7
authored
Jun 06, 2019
by
Lucas Charles
Committed by
Evan Read
Jun 06, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update PROCESS.md - fix grammar
parent
262a1ca1
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
PROCESS.md
PROCESS.md
+2
-2
No files found.
PROCESS.md
View file @
35ff10f7
...
@@ -113,7 +113,7 @@ corresponding exception request to be created.
...
@@ -113,7 +113,7 @@ corresponding exception request to be created.
A level of common sense should be applied when deciding whether to have a feature
A level of common sense should be applied when deciding whether to have a feature
behind a feature flag off or on by default.
behind a feature flag off or on by default.
The following guidelines
s
can be applied to help make this decision:
The following guidelines can be applied to help make this decision:
*
If the feature is not fully ready or functioning, the feature flag should be disabled by default.
*
If the feature is not fully ready or functioning, the feature flag should be disabled by default.
*
If the feature is ready but there are concerns about performance or impact, the feature flag should be enabled by default, but
*
If the feature is ready but there are concerns about performance or impact, the feature flag should be enabled by default, but
...
@@ -125,7 +125,7 @@ For more information on rolling out changes using feature flags, read [through t
...
@@ -125,7 +125,7 @@ For more information on rolling out changes using feature flags, read [through t
In order to build the final package and present the feature for self-hosted
In order to build the final package and present the feature for self-hosted
customers, the feature flag should be removed. This should happen before the
customers, the feature flag should be removed. This should happen before the
22nd, ideally _at least_ 2 days before. That means MRs with feature
22nd, ideally _at least_ 2 days before. That means MRs with feature
flags being picked at the 19th would have
a quite
tight schedule, so picking
flags being picked at the 19th would have
quite a
tight schedule, so picking
these _earlier_ is preferable.
these _earlier_ is preferable.
While rare, release managers may decide to reject picking a change into a stable
While rare, release managers may decide to reject picking a change into a stable
...
...
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