diff options
| author | Drew DeVault <sir@cmpwn.com> | 2019-02-21 23:21:47 -0500 |
|---|---|---|
| committer | Drew DeVault <sir@cmpwn.com> | 2019-02-21 23:21:47 -0500 |
| commit | e7f8bb102be285c729204adbf025f5d55ea9c25a (patch) | |
| tree | 970cfdb083fc91fffb20cb7e86c8681e2951a460 /builds.sr.ht/compatibility.md | |
| parent | 8c548e986174787b28525d0b3f8878f7440dece3 (diff) | |
| download | sr.ht-docs-e7f8bb102be285c729204adbf025f5d55ea9c25a.tar.gz | |
Reword support schedule
Diffstat (limited to 'builds.sr.ht/compatibility.md')
| -rw-r--r-- | builds.sr.ht/compatibility.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/builds.sr.ht/compatibility.md b/builds.sr.ht/compatibility.md index 05daec7..76b147f 100644 --- a/builds.sr.ht/compatibility.md +++ b/builds.sr.ht/compatibility.md @@ -13,12 +13,12 @@ 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. +The support lifecycle for each build image follows 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. |