Commit a820e815 authored by Robert Speicher's avatar Robert Speicher

Merge branch 'docs-add-security-changelog-information' into 'master'

Mention security fixes on Changelog guidelines

See merge request gitlab-org/gitlab!23923
parents a2242dfb 28ec2298
...@@ -35,6 +35,8 @@ the `author` field. GitLab team members **should not**. ...@@ -35,6 +35,8 @@ the `author` field. GitLab team members **should not**.
- Any change that introduces a database migration, whether it's regular, post, - Any change that introduces a database migration, whether it's regular, post,
or data migration, **must** have a changelog entry. or data migration, **must** have a changelog entry.
- [Security fixes] **must** have a changelog entry, without `merge_request` value
and with `type` set to `security`.
- Any user-facing change **should** have a changelog entry. Example: "GitLab now - Any user-facing change **should** have a changelog entry. Example: "GitLab now
uses system fonts for all text." uses system fonts for all text."
- Performance improvements **should** have a changelog entry. - Performance improvements **should** have a changelog entry.
...@@ -289,6 +291,7 @@ and then compiling the entries into the overall `CHANGELOG.md` file during the ...@@ -289,6 +291,7 @@ and then compiling the entries into the overall `CHANGELOG.md` file during the
[release managers]: https://gitlab.com/gitlab-org/release/docs/blob/master/quickstart/release-manager.md [release managers]: https://gitlab.com/gitlab-org/release/docs/blob/master/quickstart/release-manager.md
[started brainstorming]: https://gitlab.com/gitlab-org/gitlab-foss/issues/17826 [started brainstorming]: https://gitlab.com/gitlab-org/gitlab-foss/issues/17826
[release process]: https://gitlab.com/gitlab-org/release-tools [release process]: https://gitlab.com/gitlab-org/release-tools
[Security fixes]: https://gitlab.com/gitlab-org/release/docs/blob/master/general/security/developer.md
--- ---
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment