summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSarah Groff Hennigh-Palermo <sarah.groff.palermo@gmail.com>2019-05-20 15:47:26 +0000
committersarahghp <sarah.groff.palermo@gmail.com>2019-05-20 12:13:33 -0400
commite35c28bb377a6910b667e5b7959cb903e29f260b (patch)
tree0cb32fccca8db17e2041edc3467485cc5a925968
parent4948ce1159cb31e490414e36597119d9c4749e73 (diff)
downloadgitlab-ce-patch-59.tar.gz
Move the line up in the listpatch-59
-rw-r--r--doc/development/changelog.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/changelog.md b/doc/development/changelog.md
index 97f86171b61..45b3d5a23a1 100644
--- a/doc/development/changelog.md
+++ b/doc/development/changelog.md
@@ -35,6 +35,7 @@ the `author` field. GitLab team members **should not**.
- Any user-facing change **should** have a changelog entry. Example: "GitLab now
uses system fonts for all text."
+- Any change behind a feature flag **should not** have a changelog entry. The entry should be added [in the merge request removing the feature flags](https://docs.gitlab.com/ee/development/feature_flags.html#developing-with-feature-flags).
- A fix for a regression introduced and then fixed in the same release (i.e.,
fixing a bug introduced during a monthly release candidate) **should not**
have a changelog entry.
@@ -47,7 +48,6 @@ the `author` field. GitLab team members **should not**.
- Performance improvements **should** have a changelog entry.
- Any change that introduces a database migration **must** have a
changelog entry.
-- Any change behind a feature flag **should not** have a changelog entry. The entry should be added in the merge request removing the feature flags.
## Writing good changelog entries