Blame meetings/2019/2019-09-16.md

9a113d
Attending (quorum)
9a113d
Mike McLean
9a113d
Jim Perrin
9a113d
Karsten Wade
9a113d
Johnny Hughes
9a113d
Karanbir Singh
9a113d
9a113d
Notes
9a113d
Center our reply back around impact on layered products
9a113d
Satellite, OpenStack -- layered products devel platform
9a113d
Having a Stream shift to RHEL 9 beta mid-stream is needed
9a113d
9a113d
9a113d
What does it honestly mean to have CentOS as an upstream to RHEL?
9a113d
Need all of Phase 1 to be a useful upstream and six months to shift to N+1.
9a113d
9a113d
9a113d
Timing idea
9a113d
Phase 1 -- 5 years of feature devel
9a113d
One point release into Phase 1 to help layered teams
9a113d
2 years of overlap
9a113d
Alignment
9a113d
9a113d
9a113d
9a113d
Reply
9a113d
“There needs to be a CentOS Stream version for every RHEL major release. This Stream version needs to be usable for layered projects for as long as RHEL is in Phase 1 of active development. Once a RHEL release goes to Phase 2, we need to give projects and the open source ecosystem six months to shift to the active development Stream.”
9a113d
9a113d
“A year in advance of RHEL 9 we have a Stream 9 that is public beta for RHEL. From RHEL 9 release we have 5 years of active development window. Three years into that we pick up the RHEL 10.”
9a113d
This means a version per RHEL that goes through Phase 1 then EOLs in the community.
9a113d
This means two versions of Stream. CentOS Stream Green and CentOS Stream Blue.
9a113d
One is always in the Phase 1, one becomes Alpha then moves past release
9a113d