<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 14, 2015 at 10:51 PM, Jim Perrin <span dir="ltr"><<a href="mailto:jperrin@centos.org" target="_blank">jperrin@centos.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
On 04/14/2015 03:17 PM, Marcin Dulak wrote:<br>
> Hi,<br>
><br>
> i would like to add some more to the discussion started at<br>
> <a href="http://lists.centos.org/pipermail/centos-devel/2015-April/013163.html" target="_blank">http://lists.centos.org/pipermail/centos-devel/2015-April/013163.html</a><br>
><br>
> 1.<br>
> On the plot attached to <a href="http://bugs.centos.org/view.php?id=8447" target="_blank">http://bugs.centos.org/view.php?id=8447</a><br>
> one can see that since the CentOS 7 release the number of unresolved<br>
> issues on <a href="http://bugs.centos.org" target="_blank">bugs.centos.org</a> has increased,<br>
> and the number is currently more than 50 unresolved issues per month.<br>
> Many issues do not obtain any attention (nothing in the notes).<br>
> This continues for several months, and is an unprecedented situation.<br>
<br>
</span>How is it unprecedented?<br></blockquote><div> </div><div>it looks unprecedented to me on the plot.</div><div>There has never been a time on <a href="http://bugs.centos.org">bugs.centos.org</a> with that</div><div>many bugs left open per month for such a long period of time.</div><div><br></div><div>Best regards,</div><div><br></div><div>Marcin <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
> For me it shows that the CentOS community has not enough resources to<br>
> deal with the reported issues.<br>
<br>
</span>You're right. We could absolutely use more community members willing to<br>
step up and help triage/fix/duplicate the bugs.<br>
<span class=""><br>
> From this point of view it would be better to have CentOS issues<br>
> integrated into RHEL's bugzilla,<br>
<br>
</span>Unsure what you mean here. Putting our bugs in bugzilla would simply<br>
mean we move from not responding to them on bugs.centos to not<br>
responding to them in bugzilla. We don't get any additional resources<br>
simply by using bugzilla.<br>
<span class=""><br>
<br>
<br>
<br>
><br>
> 2.<br>
> A single example I would like to bring up is the fate of<br>
> <a href="http://bugs.centos.org/view.php?id=8249" target="_blank">http://bugs.centos.org/view.php?id=8249</a><br>
> The reporter made a substantial effort to collect usability issues<br>
> encountered during an installation of CentOS,<br>
> got asked to report the issues at bugzilla what he did, and there this<br>
> got (politely) closed <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1197377" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1197377</a><br>
> This seems to be his only bug at <a href="http://bugzilla.redhat.com" target="_blank">bugzilla.redhat.com</a>.<br>
><br>
> Maybe if CentOS was at bugzilla then CentOS developers could focus more<br>
> on the "open-source" way of dealing with people's reports,<br>
> which will counteract a bit Red Hat's enforcement of compliance with<br>
> it's strategies.<br>
<br>
</span>Elaborate here please? The core system does not change. That's been a<br>
distro fundamental from the beginning. If RH closes a bug, we inherit<br>
their change (or lack thereof). SIGs are the way for groups of<br>
interested people to work together and make those changes themselves.<br>
<span class=""><br>
><br>
> 3.<br>
> One more point, and it has to do with the way Fedora/EPEL package<br>
> updates are handled.<br>
> When I update an RPM package fixing a bug for Fedora/EPEL the update<br>
> almost never gets any reviews.<br>
<br>
</span>This is a Fedora/EPEL issue, and is something we as a distro don't have<br>
any control over. We've had discussions a few times with the Fedora/EPEL<br>
folks about this but there is no simple answer or immediate fix.<br>
<span class=""><br>
> The update is sitting for some fixed amount of time (2 weeks for EPEL)<br>
> and after that I push it to stable (still without any review).<br>
> I'll bring the famous case here what the result of such releases could<br>
> potentially be:<br>
> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1054350" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1054350</a> (actually I don't<br>
> know if the offending release was reviewed or not).<br>
> Or another case which affected me:<br>
> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1063493" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1063493</a><br>
> Red Hat changed major version of software (mpich2 -> mpich3) which<br>
> resulted in a couple months of empty running reviews<br>
> (2 weeks each) at EPEL in order to fix all dependencies.<br>
<br>
</span>So step in. Contribute feedback, jump on the EPEL-devel mailing list and<br>
request feedback for packages. Join the relevant irc channels and<br>
request/give feedback.<br>
<span class=""><br>
> I'm not familiar with the role CentOS could have in the process of<br>
> preparation of new RHEL updates,<br>
<br>
</span>Effectively 0. We see the updates when they land in git, the same as<br>
everyone else.<br>
<span class=""><br>
> but if there is anything that could be done to improve the RPM package<br>
> update process,<br>
> it should be considered as an important factor in case of merging CentOS<br>
> issues to bugzilla.<br>
<br>
</span>RHEL and EPEL are quite separate, so I don't really follow what you mean<br>
here.<br>
<br>
In my eyes, there are two benefits from using rh's bugzilla vs our own<br>
tracker.<br>
<br>
1. It's one less thing to manage.<br>
2. Bugs that have upstream relevance could (in theory) be more easily<br>
tagged/cloned without asking the user to duplicate as we currently do.<br>
This is still a hypothetical, as we've not talked with the bugzilla<br>
folks yet to see how any of this would work, or what would be possible.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
--<br>
Jim Perrin<br>
The CentOS Project | <a href="http://www.centos.org" target="_blank">http://www.centos.org</a><br>
twitter: @BitIntegrity | GPG Key: FA09AD77<br>
_______________________________________________<br>
CentOS-devel mailing list<br>
<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a><br>
<a href="http://lists.centos.org/mailman/listinfo/centos-devel" target="_blank">http://lists.centos.org/mailman/listinfo/centos-devel</a><br>
</font></span></blockquote></div><br></div></div>