clarification and pre-release

README.md

@@ -13,8 +13,14 @@ build:
 * If `rllh` is set to `0` or is undefined, the stable packages are built
 * If `rllh` is set to a number higher than `0`, the lookahead packages are built
 
+When `rllh` is set to something higher than `0`, the minor version will
+typically be `y+1`. So if the current stable os `X.0`, the next would be `X.1`.
+For pre-releases, both packages should produce `X.0` until changed in the spec.
+
 The `rllh` macro may be versioned out for future use.
 
+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
@@ -22,3 +28,8 @@ 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 me in
+maintenance only mode.

SPECS/rocky-release.spec

@@ -29,7 +29,7 @@
 # will contact the mirrors or set the baseurl to properly use Rocky LookAhead,
 # otherwise, the default is "stable"
 %if 0%{?rllh}
-%define minor        1
+%define minor        0
 %define contentdir   pub/rocky-lh
 %define rltype       lookahead
 %define rlpkg        -lookahead