diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-26 12:06:18 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-26 12:06:18 +0000 |
| commit | 6a4ffad42050949fcf08e78147575734ae99627e (patch) | |
| tree | 723bb2480948ba4ec29ca9ac10f8728dc2a831b6 /doc/policy | |
| parent | 23d237110e6a646dec08e1f5b4696d2d9c51cfef (diff) | |
| download | gitlab-ce-6a4ffad42050949fcf08e78147575734ae99627e.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/policy')
| -rw-r--r-- | doc/policy/maintenance.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/policy/maintenance.md b/doc/policy/maintenance.md index ef94236d711..49f2b61a497 100644 --- a/doc/policy/maintenance.md +++ b/doc/policy/maintenance.md @@ -48,8 +48,8 @@ incremental upgrades (and installations) are as simple as possible. review process a new change goes through. 1. Ensuring that tests pass on older release is a considerable challenge in some cases, and as such is very time consuming. -Including new features in patch releases is not possible as that would break [Semantic Versioning]. -Breaking [Semantic Versioning] has the following consequences for users that +Including new features in patch releases is not possible as that would break [Semantic Versioning](https://semver.org/). +Breaking [Semantic Versioning](https://semver.org/) has the following consequences for users that have to adhere to various internal requirements (e.g. org. compliance, verifying new features and similar): 1. Inability to quickly upgrade to leverage bug fixes included in patch versions. |