On Wed, Sep 25, 2019 at 11:40:19AM -0400, Stephen Gallagher wrote: > On Tue, Sep 24, 2019 at 6:13 PM Neal Gompa <ngompa13@xxxxxxxxx> wrote: > > > > On Tue, Sep 24, 2019 at 5:54 PM Kevin Fenzi <kevin@xxxxxxxxx> wrote: > > > > > > After the announcement today of centos-stream, I wonder if it would make > > > sense to move epel8-playground to build against that instead of the > > > latest rhel8 release? > > > > > > It would make playground less usefull for testing new radical changes > > > against the current stable point release, but on the other hand, the > > > centos stream will become the next stable point release, so it would > > > allow people to test against that and get changes ready that they could > > > then push in after the next stable point release landed? > > > > > > What do folks think? Bad idea, good idea? > > I think that makes good sense; it will provide a guarantee of early > notice when an upcoming RHEL release might introduce a problematic > change (intentionally or otherwise) and provides Red Hat with feedback > and an opportunity to fix it before RHEL releases. It will also make > our minor release merge windows easier, since we should not get any > major surprises hitting only at Beta or GA. As mentioned downstream, if we want to know if epel builds ok/breaks by changes in the stream we might instead setup a koschei instance pointing to centos stream? Since as Tony indicated we don't mass rebuild or know when something would break there. > > If we decide *not* to do this, I think we need to at least have a > policy of updating the buildroot for EPEL8-playground to include the > RHEL minor release beta tree as a lesser version of the same process > as above. So, question: when say RHEL8.1beta comes out. Is the Centos 8 stream updating that? (ie, has all beta changes and continues from there?). I think we need to be very careful with beta's. If we can get security updates via centos 8 stream then great, but if not, that makes a known pool of insecure software. :( kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
