releng

#12931 Migration to the new Forge
Opened by humaton. Modified

Open
Close Issue

Hi there, let's start working on migration to the new forge.

As proposed in discussions and the infra ticket, I would like to split this repo into 2 in the new forge.
One will be called tickets and will serve the purpose of this tracker.

The other one will be called tools and will contain the sources of this repository in a new proposed structure. releng#12925

Create docs PR's to reflect the new URL's for both ticketing and tooling.

Metadata Update from @humaton:
- Issue marked as depending on: #12925

Metadata Update from @jnsamyak:
- Issue tagged with: high-gain, high-trouble

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

Metadata Update from @jnsamyak:
- Issue untagged with: sprint-0
- Issue tagged with: sprint-2

Migration Notes

  • We should use the import functionality which has Pagure exporter in it from the new forge.
  • Update documentation accordingly.
  • Open a ticket in releng to create a repo (called tickets in the releng repo).
  • When we perform the import, we can just proceed with creating the tickets.

Timeline & Process

  • Actual changes, such as the RC script adjustments, should happen post-freeze.
  • Migration to the new import should be prepared, with an announcement made one week before the freeze.
  • The migration will take place after the final freeze.

(I had a conversation with @humaton and we agreed on the above timeline)
Metadata

high-gain high-trouble sprint-2

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.