On Thu, Apr 15, 2021 at 1:01 PM Kaleb Keithley <kkeithle@redhat.com> wrote:
>
> On Thu, Apr 15, 2021 at 11:51 AM Josh Boyer <jwboyer@redhat.com> wrote:
>>
>>
Can you point to where a SIG build has landed directly in Stream?
The only SIG I really know anything about is Storage, and so far nothing from Storage is ready for c8stream.
I've just finished building Ceph, Gluster, and NFS-Ganesha for c8stream and was getting ready to pull the trigger to have hughesjr build the Centos-Release-{Ceph,Gluster,NFS-Ganesha} packages for c8stream when this came across my radar.
I
don't think you've misunderstood as much as we might be using
different terminology. Let's clarify:
Stream packages == content that will land in a future RHEL release
Stream SIG packages == content that builds *on top of* CentOS Stream,
but does not directly land in Stream (neither the buildroot or the
composes).
I was expecting that the packages I've just built would fall into the latter category.
There may certainly be cases where a SIG does work and then we include
that work at a future date into Stream (and therefore RHEL). However,
that needs to be coordinated up front.
I'm not expecting the SIG Storage packages to ever land _in_ Stream (buildroot or composes) or RHEL. Those Ceph and Gluster bits that I mentioned previously are being handled separately, elsewhere, by other people, and I'm not familiar with the mechanics of making that happen.
HTH,
--
Kaleb