The website currently fails to render the macro and presents a confusing "FreeBSD {rel142-current}-STABLE" and incorrect links.
PR: 282652
Reported by: grahamperrin@gmail.com
Details
Details
- Reviewers
jrm grahamperrin carlavilla cperciva - Group Reviewers
releng - Commits
- R9:bbf36388d0a4: website/shared/releases: Add missing version macro for FreeBSD 14.2
Diff Detail
Diff Detail
- Repository
- R9 FreeBSD doc repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
Looking at the doc commit logs, there doesn't seem to be a convention about how to prefix the component as described in the Committer's Guide. In the ports tree, when we update a port, we use category/port, which is the path in the tree. This adds a slight convenience when doing something like git log --oneline because the location of the change can be seen without showing the commit. With that, how do you feel about this commit log?
website/shared/releases: Add missing version macro
The website currently fails to render the macro and presents a confusing "FreeBSD {rel142-current}-STABLE" and incorrect links.
PR: 282652
Reported by: Graham Perrin <grahamperrin@gmail.com>Comment Actions
Sounds good!
And it gives me the lead for another TODO: the commiter's guide article could probably benefit from an additional clarification on how to build a commit message for documentation updates on the handbook and website... :)
Comment Actions
On second thought, I'm not sure we want a section for FreeBSD 14.2-STABLE when 14.2-BETA2 is available. Let's see what re@ as to say.
Comment Actions
Yes, we want that section.
Also, oops, I started using :rel142-current: without checking that it was defined. I'll add that to my release process list (bumping where.adoc to X.Y-STABLE is part of the X.Y release process).
Comment Actions
Good thinking. I was wondering whether I might be breaking some release related processes when I re-read the header this morning.