How to update AutoQA repoinfo.conf

With each new development release of Fedora (aka Branched), new package repositories are available for testing. This page describes the changes to the AutoQA 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 on the release engineering schedule.

= When to Update =

The 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 AutoQA team will be notified by the release engineering or infrastructure teams when either of the above events occur. An AutoQA TRAC ticket will be filed to request the changes (see Mass_Branching_SOP, Release_Infrastructure_SOP and End_of_life_SOP).

= What To Update =

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

 Update the the  configuration. Change the value of  to the koji tag for the next release. For example, if branching for, you would set  as shown below:  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, you would use the configuration listed below. 

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

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

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

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

= How to Update =

Please use  to generate and submit patches for review by the AutoQA development team. For information on AutoQA patch, please see AutoQA_Patch_Process