From Fedora Project Wiki
(Created page with '== Description == Changing comps == Action == 1. clone the comps repo <pre> $ git clone ssh://git.fedorahosted.org/git/comps </pre> 2. Create the new comps file for next relea...') |
No edit summary |
||
| Line 1: | Line 1: | ||
== Description == | == Description == | ||
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. | |||
== Action == | == Action == | ||
| Line 35: | Line 35: | ||
== Verification == | == Verification == | ||
One can review the logs for rawhide compose after this change to make sure the right comps file was used. | |||
== Consider Before Running == | == Consider Before Running == | ||
Nothing yet. | |||
[[Category:Release Engineering SOPs]] | [[Category:Release Engineering SOPs]] | ||
Revision as of 20:21, 3 September 2010
Description
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.
Action
1. clone the comps repo
$ git clone ssh://git.fedorahosted.org/git/comps
2. Create the new comps file for next release:
$ cp comps-f14.xml.in comps-f15.xml.in
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 comps-f15.xml.in
5. Send it up:
$ git push
Verification
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.