Re: Confusing SCM package request

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Sep 6, 2017 at 12:15 PM, Kevin Fenzi <kevin@xxxxxxxxx> wrote:
> On 09/02/2017 07:09 AM, Pierre-Yves Chibon wrote:
>> On Tue, Aug 29, 2017 at 07:48:47AM -0400, Neal Gompa wrote:
>>> On Tue, Aug 29, 2017 at 5:36 AM, Björn 'besser82' Esser
>>> <besser82@xxxxxxxxxxxxxxxxx> wrote:
>>>> Am 29.08.2017 um 11:30 schrieb Richard W.M. Jones:
>>>>>
>>>>> I'm trying to import this package into Fedora:
>>>>>
>>>>>    https://bugzilla.redhat.com/show_bug.cgi?id=1174036
>>>>>
>>>>> I went through the new process as far as I can tell and the tool just
>>>>> filed a bug and printed out the URL of the bug:
>>>>>
>>>>>    $ fedrepo-req -t 1174036 ocaml-re
>>>>>    https://pagure.io/releng/fedora-scm-requests/issue/596
>>>>>
>>>>> Do I have to wait for that request to be handled now?  The
>>>>> documentation seems to suggest that the branch should actually have
>>>>> been created, but it is not.
>>>>>
>>>>> Rich.
>>>>
>>>>
>>>> fedrepo-req currently files issues against `fedora-scm-requests` on Pagure.
>>>> You can see those issues as a kind of queue, which gets manually processed
>>>> several times a day by limb (or other scm-admins).
>>>>
>>>> The process still is the same as it used to be, just the tooling and some
>>>> technical implementations have changed.
>>>>
>>>
>>> I don't get why this isn't automated yet... We seem to be stepping
>>> closer to it without actually doing it...
>>
>> We are but so far releng asked that this is not fully automated, so we would
>> have to bring it to them if we want to change this.
>
> We use this as a final check by a human.
>
> When I was doing all these requests a few years ago, I definitely caught
> packages that were not legally allowed or had a shoddy review at this step.
>
> We can't catch everything of course, but having a trusted person check
> on the two people adding a package (submittor/reviewer) is still well
> worth the short delay IMHO.

I don't.  Your reasoning isn't wrong, but it falls down very quickly
when you take into account that there is 0 on-going review on
packages.  All it takes for someone to do a decent enough job on the
initial review to get a package in, and then they can muck about as
much as they want.  What you're catching by doing this forced delay is
rushed reviews or laziness on the part of two people.  That's not bad,
but I'm not convinced it's worth not automating.  You implicitly trust
the reviewer and sponsors already anyway.

josh
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux