|
2 | 2 |
|
3 | 3 | ## SIG Release Roadmap for 2021 and beyond
|
4 | 4 |
|
5 |
| -This document contains the SIG Release Roadmap for 2021. The status tracking can |
6 |
| -be found at the bottom. More detailed information can be found on the [SIG |
7 |
| -Release][0] and [Release Engineering][1] project boards. |
| 5 | +This document contains the SIG Release Roadmap for 2021 and beyond. More |
| 6 | +detailed information can be found on the [SIG Release][0] and [Release |
| 7 | +Engineering][1] project boards. |
8 | 8 |
|
9 | 9 | [0]: https://github.com/orgs/kubernetes/projects/23
|
10 | 10 | [1]: https://github.com/orgs/kubernetes/projects/30
|
@@ -32,20 +32,12 @@ publishing of Kubernetes related artifacts.
|
32 | 32 | The following deliverables are necessary to achieve the overall goal. Within
|
33 | 33 | the following listing, all deliverables are sorted by their priority.
|
34 | 34 |
|
35 |
| -1. **Formalize supported release platforms (Introspectable)** |
| 35 | +1. **SLSA compliance in the Kubernetes Release Process** |
36 | 36 |
|
37 |
| - https://github.com/kubernetes/sig-release/issues/1337 |
| 37 | + https://github.com/kubernetes/release/issues/2267 |
38 | 38 |
|
39 |
| - Outcome: Definition of the life cycle for currently supported Kubernetes |
40 |
| - artifacts and a guideline for the community about how to add new platforms. |
41 |
| - |
42 |
| -1. **Implement a Bill of Materials (BOM) for release artifacts (Introspectable / |
43 |
| - Secure)** |
44 |
| - |
45 |
| - https://github.com/kubernetes/release/issues/1837 |
46 |
| - |
47 |
| - Outcome: An automated formal verification of produced release artifacts for |
48 |
| - every future release. |
| 39 | + Outcome: Ensure that our release process is fully [SLSA](https://slsa.dev) |
| 40 | + compliant. |
49 | 41 |
|
50 | 42 | 1. **Enhance Kubernetes binary artifact management (Consumable)**
|
51 | 43 |
|
@@ -94,14 +86,6 @@ the following listing, all deliverables are sorted by their priority.
|
94 | 86 | Outcome: Automated builds of `deb` and `rpm` Kubernetes packages within
|
95 | 87 | community infrastructure.
|
96 | 88 |
|
97 |
| -1. **Create releases landing page (Consumable)** |
98 |
| - |
99 |
| - https://github.com/kubernetes/website/issues/20293 |
100 |
| - |
101 |
| - Outcome: A releases page that is up to date and acts as canonical place for |
102 |
| - release related information, for example links to release notes and support |
103 |
| - timelines. |
104 |
| - |
105 | 89 | 1. **Signing of release artifacts (Secure)**
|
106 | 90 |
|
107 | 91 | https://github.com/kubernetes/release/issues/914
|
@@ -134,8 +118,27 @@ the following listing, all deliverables are sorted by their priority.
|
134 | 118 |
|
135 | 119 | To get input for making Cluster API a first-class signal for upstream releases.
|
136 | 120 |
|
137 |
| -### Current Status |
| 121 | +### Done Deliverables |
| 122 | + |
| 123 | +1. **Formalize supported release platforms (Introspectable)** |
| 124 | + |
| 125 | + https://github.com/kubernetes/sig-release/issues/1337 |
| 126 | + |
| 127 | + Outcome: Definition of the life cycle for currently supported Kubernetes |
| 128 | + artifacts and a guideline for the community about how to add new platforms. |
| 129 | + |
| 130 | +1. **Implement a Bill of Materials (BOM) for release artifacts (Introspectable / |
| 131 | + Secure)** |
| 132 | + |
| 133 | + https://github.com/kubernetes/release/issues/1837 |
138 | 134 |
|
139 |
| -| Topic | Lead | Status | Target Date | Links | |
140 |
| -| ----- | ---- | ------ | ----------- | ----- | |
141 |
| -| | | | | | |
| 135 | + Outcome: An automated formal verification of produced release artifacts for |
| 136 | + every future release. |
| 137 | + |
| 138 | +1. **Create releases landing page (Consumable)** |
| 139 | + |
| 140 | + https://github.com/kubernetes/website/issues/20293 |
| 141 | + |
| 142 | + Outcome: A releases page that is up to date and acts as canonical place for |
| 143 | + release related information, for example links to release notes and support |
| 144 | + timelines. |
0 commit comments