| ... | ... | @@ -9,7 +9,7 @@ Work on ELT Platform 24 gives us real-life feedback on the initial version of EL |
|
|
|
* New workflow limits the number of stakeholders to developers responsible for Public and CCS releases.
|
|
|
|
The hope is that fewer stakeholders can make decisions faster, and the process will be more agile.
|
|
|
|
* Three phases of the software lifecycle: unstable, stabilizing, and stable are not implemented in practice.
|
|
|
|
* The idea behind introducing unstable, stabilizing, and stable phases was to gradually mature the ELT Plafrom and avoid braking changes in the late development phase.
|
|
|
|
* The idea behind introducing unstable, stabilizing, and stable phases was to gradually mature the ELT Plaform and avoid braking changes in the late development phase.
|
|
|
|
* In practice, we went quickly from an active development phase of unstable code to an almost fixed release. As a result, ELT Platform 24 wasn't suitable for development once released to the public.
|
|
|
|
* The ad-hoc alternative Platform CCS fixes that gap.
|
|
|
|
* The new ELT Platform Lifecycle is trying to satisfy those needs with Yearly and Release Streams.
|
| ... | ... | @@ -191,4 +191,4 @@ FAQ |
|
|
|
|
|
|
|
* Pinning the kernel version
|
|
|
|
* Reverting dnf transactions
|
|
|
|
* Installing a specific snapshot |
|
|
\ No newline at end of file |
|
|
|
* Installing a specific snapshot |
