From Fedora Project Wiki

This page is deprecated
All Fedora Release Engineering Documentation has moved here with source hosted along side the code in the releng pagure repository


When we start a new Fedora development cycle (when we branch rawhide) we have to create a new comps file for the new release. This SOP covers that action.


1. clone the comps repo

$ git clone ssh://

2. Create the new comps file for next release:

$ cp

3. Edit Makefile to update comps-rawhide target

- -comps-rawhide: comps-f14.xml
- -       @mv comps-f14.xml comps-rawhide.xml
+comps-rawhide: comps-f15.xml
+       @mv comps-f15.xml comps-rawhide.xml

4. Add the new comps file to source control:

$ git add

5. Edit the list of translated comps files in po/ to reflect currently supported releases.


6. Send it up:

$ git push


One can review the logs for rawhide compose after this change to make sure the right comps file was used.

Consider Before Running

Nothing yet.