summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVictor Wu <victor@gitlab.com>2017-04-10 19:23:35 +0000
committerVictor Wu <victor@gitlab.com>2017-04-10 19:23:35 +0000
commit530d17f1e207fe60d0e854fa57fb02f7c0ea4ca6 (patch)
tree6e046d359010cc2054f1779f47b8cc986e277db2
parent400c328fb3e63ae19f8822a2f02744060f73b7ad (diff)
downloadgitlab-ce-530d17f1e207fe60d0e854fa57fb02f7c0ea4ca6.tar.gz
remove stray comma [ci skip]
-rw-r--r--PROCESS.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/PROCESS.md b/PROCESS.md
index fa9e375b226..3efbb8f83ab 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -136,7 +136,7 @@ against the potential negative impact
(things breaking without enough time to comfortably find and fix them before the release on the 22nd).
When in doubt, we err on the side of _not_ cherry-picking.
-For example, it is likely that an exception will be made for a trivial 1-5 line performance improvement,
+For example, it is likely that an exception will be made for a trivial 1-5 line performance improvement
(e.g. adding a database index or adding `includes` to a query), but not for a new feature, no matter how relatively small or thoroughly tested.
Another exception example is a medium-risk feature such as a navigation change in response to significant negative community feedback from a previous release.