On 9/24/19 3:35 PM, Jim Perrin wrote: > > On 9/24/19 1:31 PM, Phil Wyett wrote: >> On Tue, 2019-09-24 at 13:25 -0700, Jim Perrin wrote: >>> On 9/24/19 11:50 AM, Fabiano Fidêncio wrote: >>>> On Tue, Sep 24, 2019 at 8:24 PM Jim Perrin <jperrin at centos.org> >>>> wrote: >>>>> Okay, now that the release is out, and everything is announced >>>>> properly. >>>>> I'm happy to answer questions about Stream. >>>> Does the Stream change the way to contributing to a specific >>>> package on CentOS? >>> "It depends". It's a snarky answer, but it's true. >>> >>>> One of the main complaints from libosinfo consumers is how outdated >>>> the library is when CentOS is released (we have upstream releases >>>> of >>>> our database monthly). What would be the best way to get our >>>> library >>>> always up-to-date taking advantage of Streams? >>> We have to realize that stream is intended to target the next RHEL >>> release, so if you didn't see packages being rapidly rebased before, >>> you >>> probably shouldn't expect that to change. If it's a simple fix, a >>> feature addition that you've backported, that sort of thing, then the >>> vision would be a pull request and discussion, with the goal of >>> having >>> that merged in. >>> >>> >> Where will primary discussion and submissions related to streams take >> place? WIl the primary be the CentOS bug tracker or Red Hat bugzilla? > The discussion will be here on the -devel mailing list. We're currently > using the CentOS bug tracker, but we have been exploring the idea of > using either RH's bugzilla, or Jira (don't make that face). > Use of RH Bugzilla might be handy as it could permit quick correlation of abrt reports across product/version/etc. Pat -- Pat Riehecky Fermi National Accelerator Laboratory www.fnal.gov www.scientificlinux.org