Page MenuHomeFreeBSD

12.4: RELEASE (not upcoming), and missing links
AbandonedPublic

Authored by grahamperrin on Jan 8 2023, 12:08 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mar 16 2024, 10:34 AM
Unknown Object (File)
Jan 12 2024, 10:48 AM
Unknown Object (File)
Dec 20 2023, 8:33 AM
Unknown Object (File)
Nov 8 2023, 2:01 AM
Unknown Object (File)
Nov 8 2023, 12:46 AM
Unknown Object (File)
Nov 7 2023, 11:35 PM
Unknown Object (File)
Oct 7 2023, 12:57 AM
Unknown Object (File)
Oct 6 2023, 11:43 PM
Subscribers

Details

Reviewers
None
Group Reviewers
docs
Doc Committers
releng
Summary

FreeBSD bug 268287, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268287.

shared/releases.adoc

website/content/en/releases/12.4R/_index.adoc

website/themes/beastie/layouts/partials/sidenav.html

Origin of the first diff here:

Test Plan

Preview in GitHub:

Consider other pages that use what's currently named shared/releases.adoc … was any such page updated, with reference to 12.4-RELEASE, after 12.4-RELEASE was announced?

Diff Detail

Repository
R9 FreeBSD doc repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

grahamperrin created this revision.

shared/releases.adoc is an AsciiDoc file, don't change the name

From the test plan:

Consider other pages that use what's currently named shared/releases.adoc … was any such page updated, with reference to 12.4-RELEASE, after 12.4-RELEASE was announced?

More specifically: consider the changes to beta lines in https://reviews.freebsd.org/D37978#change-ZGKMDKf8nj4R.

I sped through five of the eight files listed below, the /en/ files. As far as I can tell: none will be adversely affected.

% git -C /usr/doc switch main
Switched to branch 'main'
Your branch is up to date with 'origin/main'.
% git -C /usr/doc pull --ff-only
Already up to date.
% find /usr/doc/website -newerct '5 weeks ago' -type f -exec grep 'include::shared/releases' {} +
/usr/doc/website/content/ja/releases/_index.adoc:include::shared/releases.adoc[]
/usr/doc/website/content/ja/security/_index.adoc:include::shared/releases.adoc[]
/usr/doc/website/content/ja/where.adoc:include::shared/releases.adoc[]
/usr/doc/website/content/en/where.adoc:include::shared/releases.adoc[]
/usr/doc/website/content/en/releases/12.4R/readme.adoc:include::shared/releases.adoc[]
/usr/doc/website/content/en/releases/12.4R/announce.adoc:include::shared/releases.adoc[]
/usr/doc/website/content/en/releases/_index.adoc:include::shared/releases.adoc[]
/usr/doc/website/content/en/security/_index.adoc:include::shared/releases.adoc[]
%

shared/releases.adoc is an AsciiDoc file, …

@carlavilla thanks for confirming.

I made a false assumption when I could not preview a diff before the commit to my branch.

Post-commit, it's remarkable that https://github.com/grahamperrin/freebsd-doc/blob/01eebbf0fa5a28a9fdd3aef18566b8e9efba6eb9/shared/releases.adoc#L33 and https://github.com/grahamperrin/freebsd-doc/blob/01eebbf0fa5a28a9fdd3aef18566b8e9efba6eb9/shared/releases.adoc#L44 (lines 33 and 44) are not greyed-out.

For both of those, re: https://docs.asciidoctor.org/asciidoc/latest/syntax-quick-reference/#comments, my intention was a single-line comment without having an empty line before or after the comment. Can anyone tell, is my use of single-line commentary not valid?


The prior emptiness, the ambiguity, might partly explain the disorder that is (hopefully) corrected at https://github.com/grahamperrin/freebsd-doc/commit/01eebbf0fa5a28a9fdd3aef18566b8e9efba6eb9?diff=unified#diff-1f11b6e6572daca22d97764f7ba84761d3b44e046096730c87a9b16047de7f2dR66-R68.

This differential contains too much changes, I suggest commit website/content/en/releases/12.4R/_index.adoc first, Then open another fine with rebased other changes.