infra-docs-fpo/modules/release_guide/pages/sop_updating_comps.adoc
Samyak Jain e11c1191e1 [release-guide] Use attributes for release versions instead of hardcoded values.
Signed-off-by: Samyak Jain <samyak.jn11@gmail.com>
2023-03-14 10:36:39 +05:30

59 lines
1.2 KiB
Text

include::_partials/attributes.adoc[]
== Updating Comps
=== 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
. clone the comps repo
+
....
$ git clone ssh://git@pagure.io/fedora-comps.git
....
. Create the new comps file for next release:
+
[source,subs="attributes+"]
....
$ cp comps-f{branched}.xml.in comps-f{rawhide}.xml.in
....
. Edit Makefile to update comps-rawhide target
+
[source,subs="attributes+"]
....
- -comps-rawhide: comps-f{branched}.xml
- - @mv comps-f{branched}.xml comps-rawhide.xml
+comps-rawhide: comps-f{rawhide}.xml
+ @mv comps-f{rawhide}.xml comps-rawhide.xml
....
. Add the new comps file to source control:
+
[source,subs="attributes+"]
....
$ git add comps-f{rawhide}.xml.in
....
. Edit the list of translated comps files in po/POTFILES.in to reflect
currently supported releases.
+
[source,subs="attributes+"]
....
-comps-f{old_release}.xml
+comps-f{rawhide}.xml
....
. 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.