epel

#139 Permission to delete epel9-next branches if they are reachable from he epel9 branch
Closed: Fixed by churchyard. Opened by churchyard.

Closed: Fixed
Reopen Issue

Hello.

Could it please be permitted to delete the epel9-branches in:

https://src.fedoraproject.org/rpms/python-platformdirs/commits/epel9-next
https://src.fedoraproject.org/rpms/python-filelock/commits/epel9-next
https://src.fedoraproject.org/rpms/python-distlib/commits/epel9-next

They are all reachable from the epel9 branches (currently, they are identical).

Note that I don't wish to "retire" the branches with an ugly dead commit, I want to simply pretend they never existed.

The branches were created where the instructions were different. Builds were made but can be untagged, garbage collected, and forgotten.

As far as I know, removing branches requires a releng ticket. It's never been something the epel community has been able to do.
So, to change the policy and allow package admins to be able to remove branches, would be something the releng team would need to create.

Releng has the ability to do it. Here I am asking for permission. If I get permission, I'll ask releng for action.

Currently, the policy for what branches can be removed was created by FESCo. The spirit of the policy is more or less:

  • we don't delete anything that was used to build in Koji and is not reachable from other branches
  • we don't delete "regular" (e.g. f35, epel8, etc.) branches, only "accidental" (e.g. cleanup, update-to-2.3.4, refactor, etc.) ones

Here I am asking EPEL committee to grant me an exception to treat the epel9-next branch as an accidental one.

I understand what you are asking for now.
I have given this a meeting tag, so it will come up in our next meeting.
Just know that our next meeting doesn't happen until January 5, 2022.

Metadata Update from @tdawson:
- Issue tagged with: meeting

There is no rush. Thanks.

This was discussed at the EPEL Steering Committee meeting.
We approved that epel9-next branches can be retired as you requested.

We aren't sure what releng needs from us. If this issue, saying we approve, is good enough. Or if there needs to be some official documentation.

As releng what they need from the EPEL Steering Committee to approve the retiring, and we'll get it done.

Thanks: https://pagure.io/releng/issue/10516

Metadata Update from @churchyard:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

FTR this was done.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/epel/steering/issues/139

Please continue any further discussion there.
Metadata
None

meeting

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.