(→Action) |
(→Action: Fix clone URL) |
||
(One intermediate revision by one other user not shown) | |||
Line 1: | Line 1: | ||
{{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source hosted along side the code in the [https://pagure.io/releng releng pagure repository]}} | |||
== 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. | 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. | ||
Line 6: | Line 8: | ||
1. clone the comps repo | 1. clone the comps repo | ||
<pre> | <pre> | ||
$ git clone ssh://git.fedorahosted.org/git/comps | $ git clone ssh://git.fedorahosted.org/git/comps.git | ||
</pre> | </pre> | ||
Latest revision as of 09:58, 28 March 2016
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.git
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. Edit the list of translated comps files in po/POTFILES.in to reflect currently supported releases.
-comps-f12.xml +comps-f15.xml
6. 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.