-
Story
-
Resolution: Unresolved
-
Undefined
-
None
tag2distrepo is used to map tags to distrepos and is tied closely to Koji workflows. As part of the Sprint 5 plan for migrating RelEng sub-repositories, we need to evaluate and migrate this repository to Forgejo within two weeks.
—
*Phase 1: Investigation (Week 1)*
Tasks:
Identify all scripts and automation paths that depend on tag2distrepo.
Review integration points with Koji, especially any API calls or hooks.
List open issues, branches, or PRs that need to be accounted for.
Validate compatibility with Forgejo migration tooling.
*Phase 2: Implementation (Week 2)*
Tasks:
- Execute migration to Forgejo.
- Verify the following post-migration:
- All branches and commit history
- Working scripts & tag mapping functionality
- Koji workflows not broken by URL changes
- Update references in Koji-related SOPs and scripts.
- Close Pagure repository and replace with README redirect.
*Acceptance Criteria*
- Repository migrated with no data loss.
- Koji continues to correctly reference tag → distrepo mappings.
- All tooling updated to use Forgejo URLs.
- Pagure repository disabled and cleaned.