From a88bcac3eb8c33f12cdae8fb7d7694f92e7047a3 Mon Sep 17 00:00:00 2001 From: Jeremy Cline Date: Mon, 4 May 2020 15:54:59 +0000 Subject: [PATCH] Document the ark-create-release script. --- Maintainer-Guide.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/Maintainer-Guide.md b/Maintainer-Guide.md index deb7d98..f260953 100644 --- a/Maintainer-Guide.md +++ b/Maintainer-Guide.md @@ -6,10 +6,24 @@ Every release requires the maintainer to: 1. Rebase the downstream kernel patches 2. Update the configuration -3. Create a release branch/tags +3. Create a release branch and/or tag Once that is done, the result can be imported into a dist-git repository and built in Koji. +There is a script to automate the entire process which is run nightly by CI/CD. You can run it locally: + +``` +# Ensure we've got a clean check out for all the branches we're about to use +git checkout master && git pull +git checkout ark-patches && git reset --hard upstream/ark-patches +git checkout internal && git pull + +# Create a release based on "master", which tracks mainline +./redhat/scripts/ci/ark-create-release.sh master +``` + +The individual steps taken are described below for the curious. + ## Rebasing Kernel Patches The downstream kernel patches are in a branch called `ark-patches`. This branch is regularly rebased onto Linus's master branch.