Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
c83e4f3a
Commit
c83e4f3a
authored
Nov 25, 2019
by
Fabian Zimmer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fixed broken semvar links
parent
d00e35f1
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
doc/policy/maintenance.md
doc/policy/maintenance.md
+2
-2
No files found.
doc/policy/maintenance.md
View file @
c83e4f3a
...
@@ -48,8 +48,8 @@ incremental upgrades (and installations) are as simple as possible.
...
@@ -48,8 +48,8 @@ incremental upgrades (and installations) are as simple as possible.
review process a new change goes through.
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.
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].
Including new features in patch releases is not possible as that would break
[
Semantic Versioning
]
(
https://semver.org/
)
.
Breaking [Semantic Versioning] has the following consequences for users that
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):
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.
1.
Inability to quickly upgrade to leverage bug fixes included in patch versions.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment