diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-05-27 21:10:52 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-05-27 21:10:52 +0300 |
commit | 479221aa79c2e18497589f0aef175a06fb5f5e29 (patch) | |
tree | 08816013065674d37dba23fb0de010d257ae55be /doc/development/changelog.md | |
parent | f719944deedf392d98947cb1c499169696c8da70 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/changelog.md')
-rw-r--r-- | doc/development/changelog.md | 11 |
1 files changed, 10 insertions, 1 deletions
diff --git a/doc/development/changelog.md b/doc/development/changelog.md index 8e7b9868cbe..616b175c9eb 100644 --- a/doc/development/changelog.md +++ b/doc/development/changelog.md @@ -79,8 +79,17 @@ EE: true ## What warrants a changelog entry? -- Any user-facing change **should** have a changelog entry. Example: "GitLab now +- Any change that introduces a database migration, whether it's regular, post, + or data migration, **must** have a changelog entry, even if it is behind a + disabled feature flag. +- [Security fixes](https://gitlab.com/gitlab-org/release/docs/blob/master/general/security/developer.md) + **must** have a changelog entry, with `Changelog` trailer set to `security`. +- Any user-facing change **must** have a changelog entry. Example: "GitLab now uses system fonts for all text." +- Any client-facing change to our REST and GraphQL APIs **must** have a changelog entry. + See the [complete list what comprises a GraphQL breaking change](api_graphql_styleguide.md#breaking-changes). +- Any change that introduces an [Advanced Search migration](elasticsearch.md#creating-a-new-advanced-search-migration) + **must** have a changelog entry. - A fix for a regression introduced and then fixed in the same release (such as fixing a bug introduced during a monthly release candidate) **should not** have a changelog entry. |