Page MenuHomeFreeBSD

porters-handbook: remove __FreeBSD_version references for EOL FreeBSD
Needs ReviewPublic

Authored by emaste on Sun, Dec 29, 2:54 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Jan 12, 8:26 PM
Unknown Object (File)
Sat, Jan 11, 11:23 AM
Unknown Object (File)
Sat, Jan 11, 7:59 AM
Unknown Object (File)
Sat, Jan 11, 5:20 AM
Unknown Object (File)
Thu, Jan 9, 3:02 AM
Unknown Object (File)
Fri, Jan 3, 10:56 PM
Unknown Object (File)
Thu, Jan 2, 8:25 PM
Unknown Object (File)
Sun, Dec 29, 6:22 PM

Details

Reviewers
None
Group Reviewers
portmgr
Summary
Ports does not support releases before 13.x, so make this list more
manageable by trimming old entries.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

This is a reaonable suggestion, cleaning up this list when a major release goes EOL would be a good idea too.

I am not sure this is a good idea.

This list is the only definitive list of "this version corresponds to that change".

I know it will still be in the source control history, but removing the list from the doc means that someone looking for an older version will not be able to find it by just looking at the web site, they will have to know how to look at the history, and understand asciidoc.

In D48244#1101534, @mat wrote:

I am not sure this is a good idea.

This list is the only definitive list of "this version corresponds to that change".

But what possible value is there today in making it easy to find that e.g. sigset_t's type changed in September 1999? I can see an argument for keeping recently-out-of-support versions (e.g. 12.x) as some downstreams might still be using them.

We could perhaps move this to a separate section so the page isn't unwieldy, but I'd argue the information about changes in obsolete versions has essentially no value and nothing is lost by just removing it.

But what possible value is there today in making it easy to find that e.g. sigset_t's type changed in September 1999? I can see an argument for keeping recently-out-of-support versions (e.g. 12.x) as some downstreams might still be using them.

Probably no value for that particular change, but I've used the __FreeBSD_version list to look up when features were added to FreeBSD when writing about historical events. I think it's worth keeping all the old __FreeBSD_version values listed *somewhere* in documentation on the FreeBSD website even if only the recent values are relevant to the Porter's Handbook.