From 9e0e6b91cd6d8ae2043dd8e4a44bd849c0d53e56 Mon Sep 17 00:00:00 2001 From: Bradley G Smith Date: Feb 02 2024 21:26:17 +0000 Subject: Revise Workflow Introduction --- diff --git a/README.md b/README.md index d3c7f2e..c20b165 100644 --- a/README.md +++ b/README.md @@ -20,15 +20,15 @@ Kubernetes releases are tracked upstream at https://kubernetes.io/releases/. Ups Kubernetes 1.30 is available at https://copr.fedorainfracloud.org/coprs/buckaroogeek/copr-k8s-1.30/. This is an alpha level release. These rpms have the revised package layout. RPMS available for rawhide (F40) only. -Kubernetes 1.29 is available at https://copr.fedorainfracloud.org/coprs/buckaroogeek/copr-k8s-1.29/. They have a revised package layout. +Kubernetes 1.29 is available at https://copr.fedorainfracloud.org/coprs/buckaroogeek/copr-k8s-1.29/. They have a revised package layout. -Kubernetes 1.28 is available at https://copr.fedorainfracloud.org/coprs/buckaroogeek/copr-k8s-1.28/. +Kubernetes 1.28 is available at https://copr.fedorainfracloud.org/coprs/buckaroogeek/copr-k8s-1.28/. Kubernetes 1.27 is available in COPR at: https://copr.fedorainfracloud.org/coprs/buckaroogeek/copr-k8s-1.27/. ## Kubernetes Package Workflow -1 Feb 2024. The workflow to revise the spec file now uses the ```newrelease.sh``` script. This script uses a configuration file (```newrelease.conf```) and a template file for the target spec file to generate a revised spec file for use in the standard Fedora build processes. +1 Feb 2024. The workflow to revise the spec file now uses the ```newrelease.sh``` script. This script uses a configuration file (```newrelease.conf```) and a template spec file to generate a revised spec file for use in the standard Fedora build processes. Edits made directly to the spec file will be over-written during the next update cycle. ### Generate a new configuration file, if needed @@ -54,7 +54,7 @@ Kubernetes 1.27 is available in COPR at: https://copr.fedorainfracloud.org/coprs 1. Edit the template (initially ```./template/kubernetes-template.spec``` but set in configuration file) -2. Run, if appropriate, +2. Run ``` newrelease.sh -y