git: 51a6d7b6d9 - main - releases: Expand rel-latest macro

The branch main has been updated by ziaee:

URL: https://cgit.FreeBSD.org/doc/commit/?id=51a6d7b6d94e5c9e7343a6747b94914df40bd61e

commit 51a6d7b6d94e5c9e7343a6747b94914df40bd61e
Author:     Alexander Ziaee <ziaee@FreeBSD.org>
AuthorDate: 2026-04-22 17:46:13 +0000
Commit:     Alexander Ziaee <ziaee@FreeBSD.org>
CommitDate: 2026-04-22 17:46:14 +0000

    releases: Expand rel-latest macro
    
    There are a few places where we compare a RELEASE to it's STABLE branch,
    or a RELEASE to it's previous release. Use macros so we can bump these
    instead of bumping the numbers constantly.
    
    Outstanding:
    - I don't know what to do with rel-latest-previous since we're at a .0
    currently, it should be whatever the reader should update to before they
    update to 15.0. The jails chapter would benefit greatly from that.
    
    - The syntax for escaping to use a macro inside of a code block is
    still I can't figure it out... but other than that it's working well!
    
    Fixes:                  ff71b333bffa (releases: define rel-latest macro)
    Reviewed by:            mhorne
    Suggested by:           Jan Brankamp <crest@rlwinm.de>
    Differential Revision:  https://reviews.freebsd.org/D56104
---
 shared/releases.adoc | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/shared/releases.adoc b/shared/releases.adoc
index fb2830079a..9b440760df 100644
--- a/shared/releases.adoc
+++ b/shared/releases.adoc
@@ -31,8 +31,17 @@
 :rel-head-major: 16
 :rel-head: {rel-head-major}.0
 
-// Current latest RELEASE for handbook examples.
-:rel-latest: 15.0
+// Current latest production RELEASE.
+:rel-latest-major: 15
+:rel-latest: {rel-latest-major}.0
+:rel-latest-next: {rel-latest-major}.1
+:rel-latest-previous: IGNORE
+
+// Current latest legacy RELEASE.
+:rel-legacy-major: 14
+:rel-legacy: {rel-legacy-major}.4
+:rel-legacy-previous: {rel-legacy-major}.5
+:rel-legacy-previous: {rel-legacy-major}.3
 
 // If there is no release currently in the release cycle (i.e. we
 // don't have something in BETAn or RCn), then change %beta.testing