releng

#13093 Migrate compose-tracker Repository from Pagure to Forgejo
Opened by jnsamyak. Modified

Open
Close Issue

compose-tracker provides tracking data and metadata for ongoing Fedora composes. It is used throughout the release cycle and cross-referenced by failed-composes, Pungi, and RelEng scripts.
This repository must be migrated during Sprint 5, following the two-phase plan (Investigation → Implementation).

Phase 1: Investigation (Week 1)
Tasks:
- Identify all integrations with Pungi, failed-composes, and internal RelEng tooling.
- Audit URLs and paths in scripts referencing compose-tracker data.
- Evaluate issue tracker metadata and migration requirements.
- Map dependencies to ensure nothing breaks post-migration.

Phase 2: Implementation (Week 2)
Tasks:
- Migrate repository to Forgejo using migration tooling.
Verify:
- Data structure and commit history
- Issue tracker, labels, milestones
- Compose tracking scripts referencing the repo
- Update all URLs in RelEng workflow scripts.
- Disable and clean Pagure repository with README redirect.

Acceptance Criteria
- Compose tracking continues without interruptions.
- All metadata and history preserved.
- All scripts updated across the RelEng ecosystem.
- Pagure repository properly closed out.

Metadata Update from @jnsamyak:
- Issue assigned to amedvede

Forgot to add one item, please also make sure to look out for the mailing list if connected, always make sure to send out an annoucment for this before moving, once you start working on it, make sure to send out "when" it will be moved so community knows about it.
Metadata

dev high-gain high-trouble investigation sprint-5

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.