Bug 213965

Summary: [patch] FAQ corrections for 11-Release.
Product: Documentation Reporter: Federico Caminiti <demian.fc>
Component: Books & ArticlesAssignee: freebsd-doc (Nobody) <doc>
Status: Closed FIXED    
Severity: Affects Only Me CC: bjk
Priority: --- Keywords: patch
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
Update the FAQ to reflect changes to 11.0 release. none

Description Federico Caminiti 2016-11-01 04:34:42 UTC 
Created attachment 176360 [details]
Update the FAQ to reflect changes to 11.0 release.

Section 1.12 (Where can I get FreeBSD?) of the FAQ contains the following sentences:

"The latest 10-STABLE release, 11.0-RELEASE can be found in the 11.0-RELEASE directory." and "The latest 9-STABLE release, 10.3-RELEASE can be found in the 10.3-RELEASE directory."

They should be changed to: 

"The latest 11-CURRENT release, 11.0-RELEASE can be found in the 11.0-RELEASE directory." and "The latest 10-STABLE release, 10.3-RELEASE can be found in the 10.3-RELEASE directory."

The attached patch applies the propposed change and updates the title of the FAQ to reflect the fact that it covers FreeBSD 11.x as well as 9.x y 10.x.

[1] https://www.freebsd.org/doc/faq/introduction.html#idp55357672
Comment 1 Benjamin Kaduk freebsd_committer freebsd_triage 2016-11-01 17:06:47 UTC 
(11-CURRENT does not exist anymore, for what it's worth; we have 11-STABLE and 12-CURRENT, now.  But the 10/11 mismatch you note is still valid.)
Comment 2 Federico Caminiti 2016-11-02 05:21:03 UTC 
(In reply to Benjamin Kaduk from comment #1)

You're right, I'm still not used to 12-CURRENT and didn't notice. For context, I found this while trying to update a translation. This means the attached patch is wrong. I used the entities that were already defined a the top of the document, so the actual solution probably involves modifying the entities (or adding new ones).

I found this also happens in Advanced Topics (1) (What are snapshots and releases? ). It may happen in other places too, I haven't checked thoroughly. 

I can resend the patch, but I don't know what the right approach is here (9-STABLE EOLs in less than two months, so perhaps it can be removed then).


[1] https://www.freebsd.org/doc/faq/advanced.html
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2018-01-01 00:36:03 UTC 
This has since been fixed. Thanks for the report.