[CentOS-devel] Hosting CentOS bugs on RH bugzilla

On 04/14/2015 05:46 PM, Nico Kadel-Garcia wrote:
> On Tue, Apr 14, 2015 at 4:51 PM, Jim Perrin <jperrin at centos.org> wrote:
> 
>> So step in. Contribute feedback, jump on the EPEL-devel mailing list and
>> request feedback for packages. Join the relevant irc channels and
>> request/give feedback.
> 
> Some of us try. There is a serious learning curve for Fedora and EPEL
> to get involved in publishing patches to their code: I've tried on at
> least 3 distinct occassions, and gotten bogged down every time in the
> "koji" setups. "Look it up on the web" doesn't help, and IRC is not
> documentation. The variety of bugzillas and credentials needed for the
> multiple systems, CentOS, RHEL, Fedora, EPEL, etc. all get confusing.
> 
>>> I'm not familiar with the role CentOS could have in the process of
>>> preparation of new RHEL updates,
>>
>> Effectively 0. We see the updates when they land in git, the same as
>> everyone else.
> 
> I'm going to be very confused if you do not, individually, have RHEL
> licenses for early RPM and SRPM review. Are you saying that the git
> repo updates occur simultaneously, or before, RPM and SRPM publication
> for RHEL customers? I can imagine "clean room" reasons to avoid access
> for CentOS core developers, but as a DevOps guy, I'll be surprised.

Stand by to be surprised ... the first time I see any code from Red Hat
that goes into CentOS is when it lands in git.centos.org (or for older
distros, ftp.redhat.com).

Community members of the QA channel can verify that we send information
into that channel when updates are found on ftp or git.  I then build
and push the updates.

I do not have a RHEL subscription or access to RHEL SRPMS from inside
RHN and I never have.

I build almost every SRPM that gets released into every CentOS version,
and my access to these things is unchanged from what it was 1, 2, 5, or
10 years ago.

<snip>

Thanks,
Johnny Hughes

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20150414/02807919/attachment-0004.sig>