On Mon, 13 Dec 2021 at 22:20, Matthew Miller <mattdm(a)fedoraproject.org> wrote:
On Mon, Dec 13, 2021 at 09:40:19AM -0500, Stephen John Smoogen wrote:
> It is a fairly manual process where a person volunteers to sit in
> front of the firehose every day and deal with these requests. The
> person who has to process them has a checklist of policy items they
> have to confirm/check to make sure the branch is possible.
Where is that checklist? I found
I don't know myself.
https://docs.pagure.org/releng/sop_process_dist_git_requests.html,
but it
refers to a tool which is deprecated in favor of another one, at
https://pagure.io/fedscm-admin/, but none of those places have a clear
articulation of the policy items.
I get human sanity check of new package requests is good, although really
ideally I would hope that wouldn't fall to the rel-eng/scm firehose
volunteers.
But it seems like "request an EPEL branch" should generally be either
"Okay!
Doing that automatically now" or "Oh, this is in EL, sorry"*. What are
the
other cases?
As far as I know this isn't about requesting EPEL branches, as much as
requesting any branches by hand. If I add something to Fedora rawhide
and then ask for a F34 branch, the same issues can happen. Remember
our build infrastructure is a pile of band-aids on top of duct tape on
top of bungee cords. Lots of tools are written for a toolchain which
existed years ago and have been hacked to make it work with whatever
new initiative that comes into play. 'Unexpected' side effects and
corner cases happen all the time and the fixing of them tends to add
new ones.
* I'm very sad that this isn't "So, would you like to do it anyway, and
then
make a module?", but c'est la vie
--
Stephen J Smoogen.
Let us be kind to one another, for most of us are fighting a hard
battle. -- Ian MacClaren