|
25 | 25 | - [Test Plan](#test-plan)
|
26 | 26 | - [Graduation Criteria](#graduation-criteria)
|
27 | 27 | - [Alpha](#alpha)
|
28 |
| - - [Alpha -> Beta Graduation](#alpha---beta-graduation) |
29 |
| - - [Beta -> GA Graduation](#beta---ga-graduation) |
| 28 | + - [Alpha -\> Beta Graduation](#alpha---beta-graduation) |
| 29 | + - [Beta -\> GA Graduation](#beta---ga-graduation) |
30 | 30 | - [Upgrade / Downgrade Strategy](#upgrade--downgrade-strategy)
|
31 | 31 | - [Version Skew Strategy](#version-skew-strategy)
|
32 | 32 | - [Implementation History](#implementation-history)
|
33 |
| -- [Drawbacks [optional]](#drawbacks-optional) |
34 |
| -- [Alternatives [optional]](#alternatives-optional) |
| 33 | +- [Drawbacks \[optional\]](#drawbacks-optional) |
| 34 | +- [Alternatives \[optional\]](#alternatives-optional) |
35 | 35 | <!-- /toc -->
|
36 | 36 |
|
37 | 37 | ## Release Signoff Checklist
|
@@ -204,14 +204,17 @@ to interact via the web interface. Currently there are no (Go) libraries that we
|
204 | 204 |
|
205 | 205 | #### OBS configuration and packages layout
|
206 | 206 |
|
207 |
| -Packages will be published for the following Debian-based (`apt`) and RPM-based (`yum`) distributions and architectures: |
| 207 | +We'll publish Debian-based (`deb`) and RPM-based (`rpm`) packages. Packages will be published for the following |
| 208 | +architectures: `aarch64`, `armv7l`, `ppc64le`, `s390x`, `x86_64`. We'll build packages on the following operating |
| 209 | +systems and architectures: |
208 | 210 |
|
209 | 211 | - Ubuntu 20.04 (`aarch64`, `armv7l`, `ppc64le`, `s390x`, `x86_64`)
|
210 | 212 | - CentOS Stream 8 (`aarch64`, `ppc64le`, `x86_64`)
|
211 | 213 | - OpenSUSE Factory (`armv7l`, `s390x`)
|
212 | 214 |
|
213 |
| -Those operating systems are supposed to provide the best compatibility with all Debian-based and RPM-based |
214 |
| -distributions, respectively. |
| 215 | +Note: those operating systems are used as **builders**. The resulting packages are supposed to work on any Debian-based |
| 216 | +and RPM-based distribution, respectively. Those distributions were chosen based on recommendations from the OBS team |
| 217 | +to provide the best compatibility with all all Debian-based and RPM-based distributions. |
215 | 218 |
|
216 | 219 | The following packages will be published for all operating system and architectures listed earlier. For simplicity,
|
217 | 220 | we'll refer to those as packages as the **core packages**:
|
@@ -321,7 +324,7 @@ The RPM specs will be generated by `kubepkg`, which already supports this. We on
|
321 | 324 |
|
322 | 325 | As described above, currently, it's up to the Release Manager to create the subproject and packages structure in OBS
|
323 | 326 | before releasing the first alpha release. This should be the only manual steps required by Release Managers (besides
|
324 |
| -the user management, described below). |
| 327 | +the user management, described below). We'll consider automating those steps in the future if possible. |
325 | 328 |
|
326 | 329 | The workflow for publishing packages is:
|
327 | 330 |
|
|
0 commit comments