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.