Skip to content

Commit

Permalink
Merge pull request #75 from bgilbert/checklist
Browse files Browse the repository at this point in the history
release-checklist: add instructions for updating Fedora RPM
  • Loading branch information
bgilbert authored Feb 3, 2020
2 parents 3f9554c + daa19f8 commit 7c6c453
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions .github/ISSUE_TEMPLATE/release-checklist.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

0 comments on commit 7c6c453

Please sign in to comment.