Merge pull request #1320 from bgilbert/checklist

templates/release-checklist: improvements and cleanups
coreos · Feb 23, 2022 · d3c09e3 · d3c09e3
2 parents ec526d2 + b88ddd9
commit d3c09e3
Showing 1 changed file with 31 additions and 5 deletions.
diff --git a/.github/ISSUE_TEMPLATE/release-checklist.md b/.github/ISSUE_TEMPLATE/release-checklist.md
@@ -9,26 +9,35 @@ Tagging:
  - [ ] Run `./tag_release.sh <vX.Y.z> <git commit hash>`
  - [ ] Push that tag to GitHub
 
-Packaging:
+Fedora packaging:
  - [ ] Update the Ignition spec file in [Fedora](https://src.fedoraproject.org/rpms/ignition):
    - Bump the `Version`
    - Switch the `Release` back to `1%{?dist}`
    - Remove any patches obsoleted by the new release
    - Run `go-mods-to-bundled-provides.py | sort` while inside of the Ignition directory you ran `./tag_release` from & copy output into spec file in `# Main package provides` section
-   - Update change log
+   - Update changelog
  - [ ] Run `spectool -g -S ignition.spec`
  - [ ] Run `kinit your_fas_account@FEDORAPROJECT.ORG`
  - [ ] Run `fedpkg new-sources tarball-name`
  - [ ] PR the changes in [Fedora](https://src.fedoraproject.org/rpms/ignition)
- - [ ] Once the PR merges to rawhide, merge rawhide into the other relevant branches (e.g. f30) then push those
+ - [ ] Once the PR merges to rawhide, merge rawhide into the other relevant branches (e.g. f35) then push those, for example:
+   ```bash
+   git checkout rawhide
+   git pull --ff-only
+   git checkout f35
+   git merge --ff-only rawhide
+   git push origin f35
+   ```
  - [ ] On each of those branches run `fedpkg build`
  - [ ] Once the builds have finished, submit them to [bodhi](https://bodhi.fedoraproject.org/updates/new), filling in:
    - `ignition` for `Packages`
    - Selecting the build(s) that just completed, except for the rawhide one (which gets submitted automatically)
-   - Writing brief release notes like "New upstream release. See release notes at `link to NEWS on GH tag`"
+   - Writing brief release notes like "New upstream release; see release notes at `link to 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` which the appropriate severity.
+   - `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.
+ - [ ] [Submit a fast-track](https://github.com/coreos/fedora-coreos-config/actions/workflows/add-override.yml) for FCOS testing-devel
+ - [ ] [Submit a fast-track](https://github.com/coreos/fedora-coreos-config/actions/workflows/add-override.yml) for FCOS next-devel if it is [open](https://github.com/coreos/fedora-coreos-pipeline/blob/main/next-devel/README.md)
 
 GitHub release:
  - [ ] Wait until the Bodhi update shows "Signed :heavy_check_mark:" in the Metadata box.
@@ -48,3 +57,20 @@ GitHub release:
 Quay release:
   - [ ] Visit the [Quay tags page](https://quay.io/repository/coreos/ignition-validate?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
+
+RHCOS packaging for the current RHCOS development release:
+ - [ ] Update the Ignition spec file
+   - Bump the `Version`
+   - Switch the `Release` back to `1%{?dist}`
+   - Remove any patches obsoleted by the new release
+   - Run `go-mods-to-bundled-provides.py | sort` while inside of the Ignition directory you ran `./tag_release` from & copy output into spec file in `# Main package provides` section
+   - Update changelog
+ - [ ] Run `spectool -g -S ignition.spec`
+ - [ ] Run `kinit your_account@REDHAT.COM`
+ - [ ] Run `rhpkg new-sources tarball-name`
+ - [ ] PR the changes
+ - [ ] Get the PR reviewed and merge it
+ - [ ] Update your local repo and run `rhpkg build`
+
+CentOS Stream 9 packaging:
+  - [ ] To be written