Hey everyone, The Fedora Release Engineering (RelEng) team is happy to share that we’re entering the final phase of our migration from Pagure to Forgejo, Fedora’s new code and issue hosting platform. Over the past few months, Fedora Infrastructure and RelEng have collaborated to align our repositories and workflows with Forgejo. With the Fedora 43 Final Release is now successfully out; we’re ready to make this transition official.
## Migration Date We’re planning to migrate on November 18, 2025, which is two weeks from today. Here’s what will happen on that date: - All open and closed issues from our existing Pagure RelEng repository will be migrated to a new Forgejo repository called tickets. - Once verified, the Pagure issue tracker will be closed and replaced with a README notice directing users to Forgejo. - After that, all new Fedora RelEng issues should be filed only on Forgejo. ## What’s Changing This migration includes: - The main RelEng repository (already mirrored on Forgejo). - The RelEng issue tracker, moving to a dedicated repository called tickets. - Follow-up migrations for related repositories such as faint, composes, and others, which we’ll handle gradually once the main migration is complete. Mostly all issues, labels, milestones, and metadata will be carried over using the Forgejo migration feature. ## Communication and Coordination Ahead of the migration, we’ll be sharing reminders and updates through announcements, but we also have a tracking ticket for this in releng: https://pagure.io/releng/issue/13061. ## What You Need to Do For now, nothing. Just note that after November 17, please avoid opening new RelEng issues on Pagure, since they won’t be migrated. We’ll share the Forgejo link as soon as the migration completes. But post migration, the scripts will go in: https://forge.fedoraproject.org/releng/tooling (This move is done as part of initial restructuring work) The ticket will be filed at: https://forge.fedoraproject.org/releng/tickets In case of any issues, please poke me, or you know where to find the releng issue tracker and the channel, if not, here you go: Current Issue Tracker: https://pagure.io/releng/ Ping at: #releng:fedoraproject.org Thanks, Samyak Jain Fedora Release Engineering -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
