From ef2261863e904688e41ca751f2b8b097b4ddafea Mon Sep 17 00:00:00 2001 From: Jonathan Lebon Date: Fri, 3 Nov 2023 09:46:21 -0400 Subject: [PATCH] templates/rebase: document final `next` release before GA This is what we do in practice but it wasn't documented. --- .github/ISSUE_TEMPLATE/rebase.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/rebase.md b/.github/ISSUE_TEMPLATE/rebase.md index 0aad580..599c53f 100644 --- a/.github/ISSUE_TEMPLATE/rebase.md +++ b/.github/ISSUE_TEMPLATE/rebase.md @@ -70,6 +70,12 @@ Branching is when a new stream is "branched" off of `rawhide`. This eventually b ## Preparing for Fedora (N) GA +### Ship a final `next` release + +If the packages in `next-devel` don't exactly match the last `next` release that was done, we need to do a release with the final GA content. This ensures that what we'll promote to `testing` has the exact content in GA (plus version fast-tracks). This usually happens on the Thursday of the announcement of Go. + +- [ ] Ensure final `next` release has GA content + ### Update [fedora-coreos-config](https://github.com/coreos/fedora-coreos-config/) `testing-devel` - [ ] Bump `releasever` in `manifest.yaml`