Page MenuHomeFreeBSD

HW Relnotes: Enable Table of Contents Subsections
Needs ReviewPublic

Authored by concussious.bugzilla_runbox.com on Thu, Oct 24, 5:35 AM.
Referenced Files
F102150154: D47272.diff
Fri, Nov 8, 6:06 AM
F102140893: D47272.id.diff
Fri, Nov 8, 3:13 AM
Unknown Object (File)
Sat, Nov 2, 11:40 PM
Unknown Object (File)
Tue, Oct 29, 11:19 AM
Unknown Object (File)
Mon, Oct 28, 5:23 PM
Unknown Object (File)
Mon, Oct 28, 12:05 AM

Details

Summary

I think this really helps the page. I only did the template and upcoming releases, but would be willing to do past ones for consistency if that is appropriate.

May I also (I'm thinking separate reviews):

  1. Put the TOC below the introduction?
  2. Remove or add "Architecture Support" to all subsection titles in section 2 for consistency?
  3. Rename 2.2 "32-bit x86 (i686)" for consistency with the other subsection titles (also these do not support i386 or i486.)
  4. Remove 2.3 entirely for consistency.

If this is acceptable, please git commit --author ="Alexander Ziaee <concussious@runbox.com>" so I can demonstrate my activity. Thanks!

Diff Detail

Repository
R9 FreeBSD doc repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

Re your 3, if you change the section title, I would suggest keeping "i386" since it's the name FreeBSD for the architecture itself, minimum processor generations supported regardless, and instead mention which processor generations it supports, or maybe link to the section of the release notes with that info.

Polite ping? I made this commit atomic and scoped tightly so that we can move quickly, to facilitate ease of contribution to the HW relnotes. Is this controversial?

cperciva added a subscriber: bofh.

@bofh Can you look at this and the submitter's other questions? You're in charge of release notes. :-)

Polite ping? I made this commit atomic and scoped tightly so that we can move quickly, to facilitate ease of contribution to the HW relnotes. Is this controversial?

Sorry, been busy with other stuff. Hopefully Moin can handle this and your other release notes changes.

Copy! No problem, thank you for the quick response! I'll tag him in the future.