šŸ§­ Fedora Release Engineering is migrating to Forgejo!

Project Discussion
1

Hey everyone! :waving_hand:

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 been working together to align our repositories and workflows with Forgejo. With the Fedora 43 Final Release now successfully out, weā€™re ready to make this transition official.

:spiral_calendar: Migration Date

Weā€™re planning to migrate on November 18, 2025, which is approximately two weeks.

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.

:puzzle_piece: 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 failed-composes, and other 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.

:megaphone: 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

:raising_hands: 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 tracket and the channel, if not, here you go:

Current Issue Tracker: https://pagure.io/releng/
Ping at: #releng:fedoraproject.org
Thanks,
Samyak Jain

5 Likes
2

I wonder if open tickets in Pagure can receive a comment saying ā€œYou can now find this ticket at $URLā€?

3 Likes
3

We can do that. I was eventually planning to just turn off the ā€œissuesā€ section from setting, and add a redirect link in the parent README.

1 Like
4

Yes, but if people have direct links to issues, those will still work, right? And if such people arrive at an old issue, it would be nice to have a redirect link in the last comment (or alternatively, redirect the whole old URL to the new URL using HTTP). Iā€™m not asking just about releng tickets, Iā€™m also wondering about QA tickets. If such a feature is available, I believe weā€™d like to use it.

3 Likes
5

@kparal, Iā€™ve definitely a lot of URIs that would become 404s if issues were merely disabled. A comment or redirect is ideal.

1 Like
6

IMHO at least initially it might be better to add a big thing to readme
and just set the issues to ā€˜read-onlyā€™. That way they are there if
someone needs them.

At some point then probibly redirecting them would be ok, but managing
all the redirects is going to be kinda painfulā€¦

1 Like
7

Right, thatā€™s why I suggested to add a comment with a new link to all/just open tickets (all is maybe better, why not allā€¦) before switching them to read only. The continuity is then ensured.

Is that a currently implemented feature, or would it need to be created first?

8

This is now tracked here: https://forge.fedoraproject.org/forge/forge/issues/277

9

Hello. :waving_hand:
Another RelEng repository that will be migrated to the new forge in the near future is pungi-fedora [1].
I just finished the investigation phase and am currently formulating a more detailed plan for the implementation.
The tracker ticket can be found here [2].

[1] Making sure you're not a bot!
[2] https://forge.fedoraproject.org/releng/tickets/issues/13090

10

It looks like pungi-fedora uses CI (currently via Zuul). Is that supported yet on Forge?

11

Hey All
Tomorrow, one more repository will be migrated. Itā€™s a compose-tracker. It is sending the issues to the failed-composes. It will also be migrated soon after compose-tracker, because it requires creating compose_tracker_forgejo_token_stg and compose_tracker_forgejo_token_stg In a private Ansible repo and requires rewriting a little compose-tracker script so it could work with Forgejo. The tracker ticker can be found here[1][2]

[1] Making sure you're not a bot!
[2] Making sure you're not a bot!