[
https://issues.apache.org/jira/browse/TS-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375620#comment-15375620
]
Jon Sime commented on TS-4617:
------------------------------
Merged
https://github.com/apache/trafficserver/commit/bffb3dd4b68a0a6568f956944f01b68e6efb926a
which supports release-branch neutral configurations of available
languages/versions for documentation. Falls back to a local docbuild compatible
path so that the switcher will work seamlessly for both our official public
docs site and any local working copies for people editing the docs.
The commit above will need to be backported to our previous release branches
(at least the ones we do docbuilds for), but then we shouldn't have to touch
those branches again when we add new releases, or even new languages.
> separate documentation language/version selections into central config
> ----------------------------------------------------------------------
>
> Key: TS-4617
> URL: https://issues.apache.org/jira/browse/TS-4617
> Project: Traffic Server
> Issue Type: Improvement
> Components: Documentation
> Reporter: Jon Sime
> Assignee: Jon Sime
> Fix For: Docs
>
>
> Adding a new release, or a language, to the documentation should not require
> backporting thatsphinx template change to all prior releases (as it currently
> does). Storing the list of valid languages and versions in a central config
> that can be magicked in by a little bit of javascript (common to all
> releases' documentation templates) would let us avoid perpetual backporting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
