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: docs/src/index.md
-18
Original file line number
Diff line number
Diff line change
@@ -11,24 +11,6 @@ Pages = ["index.md"]
11
11
Depth = 5
12
12
```
13
13
14
-
## Releases
15
-
16
-
````@eval
17
-
using Docs
18
-
19
-
version = releaseVersion()
20
-
21
-
t = raw"""
22
-
Your are currently reading the documentation for the metal-stack `%s` release.
23
-
"""
24
-
25
-
markdownTemplate(t, version)
26
-
````
27
-
28
-
Releases and integration tests are published through our [release repository](https://github.com/metal-stack/releases). You can also find the [release notes](https://github.com/metal-stack/releases/releases) for this metal-stack version in there. The release notes contain information about new features, upgrade paths and bug fixes.
29
-
30
-
If you want, you can sign up at our Slack channel where we are announcing every new release. Often, we provide additional information for metal-stack administrators and adopters at this place, too.
31
-
32
14
## Why metal-stack?
33
15
34
16
Before we started with our mission to implement the metal-stack, we decided on a couple of key characteristics and constraints that we think are unique in the domain (otherwise we would definitely have chosen an existing solution).
Your are currently reading the documentation for the metal-stack `%s` release.
10
+
"""
11
+
12
+
markdownTemplate(t, version)
13
+
````
14
+
15
+
Releases and integration tests are published through our [release repository](https://github.com/metal-stack/releases). You can also find the [release notes](https://github.com/metal-stack/releases/releases) for this metal-stack version in there. The release notes contain information about new features, upgrade paths and bug fixes.
16
+
17
+
If you want, you can sign up at our Slack channel where we are announcing every new release. Often, we provide additional information for metal-stack administrators and adopters at this place, too.
18
+
19
+
## Update Policy
20
+
21
+
For new features and breaking changes we create a new minor release of metal-stack. For every minor release we present excerpts of the changes in a corresponding blog article published on metal-stack.io. It is not necessary to cycle through the patch releases if you depend on the pure metal-stack components.
22
+
23
+
In case you depend on the Gardener integration though, especially when using metal-stack roles for deploying Gardener, it may be necessary to cycle through the patch release versions of our metal-stack releases. We regularly increment our Gardener dependency version by version which is the recommended way to update Gardener.
24
+
25
+
!!! warning
26
+
27
+
If you use the Gardener integration of metal-stack do not skip patch releases.
0 commit comments