From daa19f800c9e10690ebfd80d032e5d6be30a0b72 Mon Sep 17 00:00:00 2001 From: Benjamin Gilbert Date: Sat, 1 Feb 2020 01:31:18 -0500 Subject: [PATCH] release-checklist: add instructions for updating Fedora RPM Based on the Ignition ones. --- .github/ISSUE_TEMPLATE/release-checklist.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/release-checklist.md b/.github/ISSUE_TEMPLATE/release-checklist.md index f9761ccc..0995f7a9 100644 --- a/.github/ISSUE_TEMPLATE/release-checklist.md +++ b/.github/ISSUE_TEMPLATE/release-checklist.md @@ -17,3 +17,14 @@ for each release artifact. Do not try to sign all of them at once by globbing. I - Update the `release` tag on Quay: - [ ] Visit the [Quay tags page](https://quay.io/repository/coreos/fcct?tab=tags) and wait for a versioned tag to appear - [ ] Click the gear next to the tag, select "Add New Tag", enter `release`, and confirm + - Update Fedora RPM: + - [ ] Create a PR to bump the FCCT spec file in [Fedora](https://src.fedoraproject.org/rpms/fedora-coreos-config-transpiler). + - [ ] Once that PR merges to `master`, merge `master` into the other relevant branches (e.g. `f31`) then push those. + - [ ] On each of those branches (including `master`) run `fedpkg build` + - [ ] Once the builds have finished, submit them to [Bodhi](https://bodhi.fedoraproject.org/updates/new), filling in: + - `fedora-coreos-config-transpiler` for `Packages` + - Selecting the build(s) that just completed, except for the Rawhide one (which gets submitted automatically) + - Copy relevant part of release notes from the GitHub release + - Leave `Update name` blank + - `Type`, `Severity` and `Suggestion` can be left as `unspecified` unless it is a security release. In that case select `security` with the appropriate severity. + - `Stable karma` and `Unstable` karma can be set to `2` and `-1`, respectively.