From 534410aa40fb0f623cf88360989d4a7921ae8dcc Mon Sep 17 00:00:00 2001 From: Louis Abel Date: Wed, 21 Feb 2024 00:00:14 -0700 Subject: [PATCH] update readme --- README.md | 21 ++++++++------------- 1 file changed, 8 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index f0d141e..28dcfd7 100644 --- a/README.md +++ b/README.md @@ -1,12 +1,12 @@ -Release package - All PR's should be against original/rpms/rocky-release +Release package - All PR's should be against staging/src/rocky-release ## Notes for Packagers/Builders -This package produces multiple variants of `rocky-release`: +This package can produce multiple variants of `rocky-release`: * Stable: `rocky-release`, `rocky-repos`, `rocky-gpg-keys`, etc * LookAhead: All packages appended with `-lookahead` -* Beta: All packages appended with `-Beta` +* Beta: All packages appended with `-beta` * If `--with=rllookahead` or `--with=rlbeta` are set in mock, those variants are built * If both are set the same time, build will fail @@ -22,16 +22,11 @@ A `rllh_minor` macro may be introduced in the future. ### How does this benefit us? -It allows us to track future minor releases from Stream and see how it will -affect us going forward. When a minor release is being branched, the "lookahead" -files can just be copied and a new "stable" release is made in preparation. The -beta of each RHEL tends to stick around for a month before a release is done, -which makes it easier to make sure everything "stays in line" for the most part. - -### What about after the five year mark? - -LookAhead will no longer be produced as the major version will then be in -maintenance only mode. +It provides an opportunity to do self testing of various kinds. In most cases, +a rocky-release package for the upcoming minor release will be built normally +and doesn't require the variant release packages. However, the option is at +least available for those who want to test something in particular and override +the default rocky-release packages. ### What is the rloverride macro?