How to update yumrepoinfo.conf in Taskotron

Taskotron development reached end of life
Taskotron has been sunset in Fedora Infrastructure. It is no longer running and no longer being developed. You can use these wiki pages to learn about its history, but please be aware that the information is no longer actual.

With each new development release of Fedora (aka Branched), new package repositories are available for testing. This page describes the changes to the Taskotron yumrepoinfo.conf file needed to accommodate a new release of Fedora.

Introduction

Leading up to each release, the rawhide development stream is branched. Branching results in two parallel development streams, called rawhide and branched. As always, rawhide continues to track the latest and greatest development intended for future releases of Fedora. While, branched is intended for stabilization of the upcoming Fedora release.

The branch date can be found in the release schedule.

When to Update

The yumrepoinfo.conf file will need to change whenever a new package repository is available, the location of an existing repository changes or we no longer want to support an existing repository. The most common scenarios where this happens are:

1. When Fedora branches to stabilize the upcoming Fedora release
2. When Fedora is released
3. When Fedora support has ended (it's EOL'd)

The Taskotron team will be notified by the release engineering or infrastructure teams when either of the above events occur. A Taskotron ticket will be filed to request the yumrepoinfo.conf changes (see Mass Branching SOP#Taskotron, Infra Releases SOP and End of life SOP#Taskotron_tasks).

What To Update

New Fedora Branch

When a new Fedora branch release is available, the following changes are required.

1. Update the the [rawhide] configuration. Change the value of tag to the koji tag for the next release. For example, if branching for Fedora 41, you would set tag = f42 as shown below:

   [rawhide]
   url = %(rawhideurl)s
   path = development/rawhide
   tag = f42
   release_status = rawhide
   

2. Create new config sections for the current branch. A section will be needed for each of the package repositories available. For example, if branching for Fedora 41, you would use the configuration listed below.

   [f41]
   url = %(rawhideurl)s
   path = development/41
   tag = f41
   release_status = branched
   
   [f41-updates]
   url = %(updatesurl)s
   path = 41
   parent = f41
   tag = f41-updates
   
   [f41-updates-testing]
   url = %(updatesurl)s
   path = testing/41
   parent = f41-updates
   tag = f41-updates-testing
   

3. If primary or alternate architectures changed for Rawhide/Branched, make sure to locate primary_arches and alternate_arches keys in the [DEFAULT] section and update them to match Rawhide status. Then include them in any other section for which the default value is not correct (the value in a particular section will override the value from the default section).

New Fedora Release

When a new release of Fedora is available, the following changes are required.

1. Update the existing configuration for the recently released version of Fedora. For example, if Fedora 40 was just released, you would need to update the values for path and url as listed below.

   [f40]
   url = %(goldurl)s
   path = 40
   tag = f40
   release_status = stable
   

Fedora support ended

When a Fedora release reaches its End of Life (EOL), the following changes are required.

1. Remove the sections corresponding to the EOL'd release. For example, when Fedora 38 reaches EOL, the following sections would be removed:

   [f38]
   url = %(goldurl)s
   path = 38
   tag = f38
   release_status = stable
   
   [f38-updates]
   url = %(updatesurl)s
   path = 38
   parent = f38
   tag = f38-updates
   
   [f38-updates-testing]
   url = %(updatesurl)s
   path = testing/38
   parent = f38-updates
   tag = f38-updates-testing