On Wed, Sep 25, 2019 at 11:16:57AM -0700, Troy Dawson wrote:
> On Wed, Sep 25, 2019 at 11:13 AM Troy Dawson <tdaw...@redhat.com> wrote:
> >
> > On Wed, Sep 25, 2019 at 8:41 AM Stephen Gallagher <sgall...@redhat.com> 
> > wrote:
> > >
> > > On Tue, Sep 24, 2019 at 6:13 PM Neal Gompa <ngomp...@gmail.com> wrote:
> > > >
> > > > On Tue, Sep 24, 2019 at 5:54 PM Kevin Fenzi <ke...@scrye.com> 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.
> > >
> > > 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.
> > >
> 
> Thinking about this I just realized "Bad Idea"
> Why?
> Because streams is always going to be changing.
> It will be almost impossible to know what buildroot a -playground
> package was built with.
> Also, the playground packages get built, whenever they get built.
> There is not set schedule.
> So a stream update could affect package D, but package D doesn't get
> built for 6 month, so we have no idea whether the stream affects
> Package D or not.
> 
We have
<https://koschei.fedoraproject.org/?order_by=state%2Cname&collection=epel8-playground>.

-- Petr

Attachment: signature.asc
Description: PGP signature

_______________________________________________
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Reply via email to