Learn more about these different git repos.
Other Git URLs
I have just noticed that Koschei does not work properly and based on analysis done by @mizdebsk, the issue was caused by F35 EOL. Therefore, could be Koschei part of this SOP?
https://docs.pagure.org/releng/sop_end_of_life.html
But also part of branching SOP, because it is missing there as well:
https://docs.pagure.org/releng/sop_branching.html
When do you need this? (YYYY/MM/DD)
When is this no longer needed or useful? (YYYY/MM/DD)
If we cannot complete your request, what is the impact?
Koschei might miss some collection when new Fedora is branched or it can misbehave, when release goes EOL.
In the past releng did not 'run' koschei but it was more of an outside volunteer group who did that work. I do not know who is 'running' koschei now.
@mizdebsk Do you know anything about this?
I am pretty sure koschei is in the 'we run it, but are not upstream for it' list. Like koji or mbs or a number of other things.
So, it would be reasonable for us to update it for normal branching activities.
Ah ok. I thought it was in the COPR camp as in 'we provide services but we don't run it'. My apologies for any confusion I caused.
Just FTR, @mizdebsk has PTO this week and I have discussed this with him prior filing this ticket and opening this ticket is the result of the discussion.
So yes, the idea was that the config should be update as part of the branching / EOL procedures.
Here is also discussed why Koschei on itself should not handle the EOL better:
https://github.com/fedora-infra/koschei/issues/351#issuecomment-1373560309
Metadata Update from @phsmoura: - Issue tagged with: low-gain, low-trouble, ops
Metadata Update from @humaton: - Issue tagged with: docs
The Koschei instance at koschei.fedoraproject.org is hosted by Fedora Infrastructure and operated by Koschei FIG (sysadmin-koschei). Currently @mizdebsk is the only member of the FIG. SLE is "low".
I used to handle all branching and EOL tasks for Koschei myself. But ideally it would be part of branching/EOL releng procedures. I should update existing Koschei SOP, make sure that Koschei can be administrated by appropriate releng group (perhaps sysadmin-releng) and then I can propose changes to appropriate releng SOPs.
We normally do this just fine and I tried to, but there was a problem with the admin pod...
Note that releng docs are in some flux moving from docs.pagure.org to docs.fedoraproject.org, but we will make sure this is in the branching sop.
It's all taken care of now.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.