aboutsummaryrefslogtreecommitdiffstats
path: root/builds.sr.ht
diff options
context:
space:
mode:
authorDrew DeVault <sir@cmpwn.com>2019-01-16 19:28:11 -0500
committerDrew DeVault <sir@cmpwn.com>2019-01-16 19:28:11 -0500
commitb10263024d94973790578cf9622111523f1079e4 (patch)
treef6a8561ec42e0efbcf9995d014c9e3ef2b885e80 /builds.sr.ht
parent10cd5d3faef71342edc0d73779fe4192b54f1dfc (diff)
downloadsr.ht-docs-b10263024d94973790578cf9622111523f1079e4.tar.gz
Add support lifecycle policy to compatibility.md
Diffstat (limited to 'builds.sr.ht')
-rw-r--r--builds.sr.ht/compatibility.md12
1 files changed, 12 insertions, 0 deletions
diff --git a/builds.sr.ht/compatibility.md b/builds.sr.ht/compatibility.md
index 0fad52c..a7f13fd 100644
--- a/builds.sr.ht/compatibility.md
+++ b/builds.sr.ht/compatibility.md
@@ -11,6 +11,18 @@ The "native" column is checked if these builds run on native hardware for that
architecture, if unchecked the builds are run on emulated hardware and may
suffer from poor performance.
+**Support lifecycle**
+
+The supported lifecycle of each build image is directly correlated with the
+upstream support cycle. Each supported upstream release is generally offered on
+sr.ht, as well as the bleeding edge or development releases if applicable. No
+sooner than two weeks after a release becomes unsupported upstream, it will be
+unsupported on builds.sr.ht - and anyone who's submitted recent builds using
+those images will get an email warning them of the impending breakage.
+
+It's recommended that you use aliases like "alpine/latest" or "debian/testing"
+rather than using a specific release in your build manifests.
+
## Alpine Linux
<table class="table table-sm table-hover">