Hi Jason,
On 12/31/2014 01:24 AM, Jason L Tibbitts III wrote:
"PN" == Parag Nemade <pnemade@xxxxxxxxxx> writes:
PN> In simple words no human is required for processing this request.
Absolutely, categorically untrue.
There are cases when it's OK. Even outside of simple sanity checking,
there are plenty more cases when it's not. Some of those cases (say,
preventing branching of packages for EPEL when they're present in some
Red Hat product) could be written into code. Some of those cases
(perhaps tracking down the owners of other branches for ACKs) can't
easily be codified.
Having never done this job I imagine you don't know how difficult or
important it is. Post-review branching is the last chance an admin has
to prevent poorly reviewed crap from getting into the distro, which
means we actually have to read the reviews (unless they're done by
someone we trust).
- J<
True. I don't know how difficult it is that is why I am trying to
understand this process. As Pierre and you stated here I am now
understanding what is this process and what are problems for automating
it. Maybe some one can write more about this process and what are the
problems that prevents automation.
Though I see this process is documented in
https://infrastructure.fedoraproject.org/infra/docs/scmadmin.txt but
above information is not added there.
Thanks for above information.
Regards,
Parag.
_______________________________________________
infrastructure mailing list
infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
