Documentation EoL for 11.0-RELEASE.
ClosedPublic

Authored by gordon on Dec 6 2017, 5:46 AM.

Diff Detail

Repository
rD FreeBSD doc repository
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
gordon created this revision.Dec 6 2017, 5:46 AM

Adding doceng

emaste added a subscriber: emaste.Dec 6 2017, 1:39 PM
linimon added a subscriber: linimon.Dec 6 2017, 3:27 PM

I should have added secteam as well. Sorry about that.

gordon updated this revision to Diff 36308.Dec 6 2017, 5:54 PM

Accommodate r51259.

remko added a subscriber: remko.Dec 6 2017, 6:27 PM

shouldn't we try to renumber the rel0.current/rel1.current stuff ? I forgot how we did that in the past though so I can be mistaken :)

Cheers
Remko

gjb added a comment.Dec 6 2017, 7:15 PM

shouldn't we try to renumber the rel0.current/rel1.current stuff ? I forgot how we did that in the past though so I can be mistaken :)

Generally, yes, but it tends to be a bit more complicated than what Gordon has proposed here.

gjb accepted this revision.Dec 6 2017, 7:15 PM
This revision is now accepted and ready to land.Dec 6 2017, 7:15 PM
gordon added a comment.Dec 6 2017, 7:18 PM
In D13392#279901, @gjb wrote:

shouldn't we try to renumber the rel0.current/rel1.current stuff ? I forgot how we did that in the past though so I can be mistaken :)

Generally, yes, but it tends to be a bit more complicated than what Gordon has proposed here.

Also, we are likely going to have multiple from the same branch supported like we did with 11.0/11.1.

Alternatively, I can just say we switched from a 0-based counting system to a 1-based counting system.

gjb added a comment.Dec 6 2017, 7:22 PM
In D13392#279901, @gjb wrote:

shouldn't we try to renumber the rel0.current/rel1.current stuff ? I forgot how we did that in the past though so I can be mistaken :)

Generally, yes, but it tends to be a bit more complicated than what Gordon has proposed here.

Also, we are likely going to have multiple from the same branch supported like we did with 11.0/11.1.

Alternatively, I can just say we switched from a 0-based counting system to a 1-based counting system.

It also may make things easier to update when the next major version is available, i.e., 12.0-RELEASE.

This revision was automatically updated to reflect the committed changes.
wblock added a comment.Dec 8 2017, 5:26 PM

We really need a better way to handle this. Perhaps a list of entities for supported releases, then during a build, concatenate them into an entity that can be used directly in the DocBook source. Then we can get away from this FIFO, or, more accurately, "it is really hard to change these" changes.

Example:
SUPPORTED_RELEASES="11.1 10.4 9.3"

generates an entity called supported.releases containing 11.1, 10.4, and 9.3. If it was just the first two, it would be 11.1 and 10.4.

Maybe we could just generate a complete usable sentence: &supported.releases.sentence; expands to Currently supported versions of &os; are 11.1, 10.4, and 9.3..

This assumes we need to have a list of separate entities for each version. Otherwise, we could just create the entity statically.