You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ci/README.md
+20Lines changed: 20 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,3 +110,23 @@ Note that you can use the `dir` parameter in `run` to define the working directo
110
110
```
111
111
112
112
Don't forget to remove separate pipelines that were created for testing.
113
+
114
+
### Versioning Guide
115
+
116
+
For creating a new release please follow the versioning guide based on the [Semantic Versioning Specification](https://semver.org/).
117
+
118
+
***Major Version** (*X*.y.z) -- incremented if any backwards incompatible changes are introduced to the public API
119
+
120
+
Used for new HAProxy **minor** versions, as they could contain breaking changes.
121
+
***Minor Version** (x.*Y*.z) -- incremented if new, backwards compatible functionality is introduced to the public API
122
+
123
+
Used when upgrading dependencies (e.g. PCRE, socat, etc.) or HAProxy **patch** versions.
124
+
***Patch Version** (x.y.*Z*) -- incremented if only backwards compatible bug fixes are introduced)
125
+
126
+
Used for documentation updates, changes in the test suite or any updates in the testing frameworks (e.g. ginkgo).
127
+
128
+
Since releases `11.16.3` and `11.17.5` the build metadata has been included into the version number. The build metadata denotes the contained HAProxy version. As an example, `11.16.2+2.6.9` means that HAProxy 2.6.9 is used.
129
+
130
+
The `haproxy-boshrelease` also contains patches (see [haproxy-patches](../haproxy-patches)). The patched version is a part of the build metadata and is denoted by appending a hyphen and key word `patched`, like `11.17.4+2.6.9-patched`.
0 commit comments