docs: add the 15.9 documentation set for all seven languages - #507
Merged
Conversation
Fess master is now 15.9.0-SNAPSHOT, so the documentation needs a 15.9 tree to receive the changes made during that development cycle. Created with ./create_version.sh 15.9, which copies the 15.8 tree for ja, en, de, fr, es, zh-cn and ko along with the ja and en image directories, and rewrites the documentation version token in the copied RST files. versions.json moves "development" to 15.9. "release" stays at 15.8 and neither "supported" nor "schedule" changes: 15.9 is not released, so it has no support window and no end-of-life date yet. This is the same shape versions.json had while 15.7 was the release and 15.8 was in development. The generated eol.rst tables are unaffected, since they are built from "supported" and "schedule". Verified that the copy is faithful: each 15.9 tree has the same files as its 15.8 counterpart, and every one of the 2127 changed lines differs from the 15.8 original only by the version token. No number corruption of the kind fixed in #428 was reintroduced, and no stray 15.8 reference remains. The OpenSearch version named throughout install/ is 3.8.0, which still matches <opensearch.version> in fess-parent on master, so no dependency version is carried over stale. Known and deliberate: the mechanical rewrite also renamed statements that record what changed in 15.8 -- the "15.8 固有の移行作業" / "Changes in 15.8" sections and roughly 250 similar lines across 14 files in the seven languages. Correcting those is a content change that does not belong in a copy this large, and is left to focused follow-up pull requests, as was done for 15.8.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fess master is now
15.9.0-SNAPSHOT, so the documentation needs a 15.9 tree to receive the changes made during that development cycle.What this does
Created with
./create_version.sh 15.9, which copies the 15.8 tree forja,en,de,fr,es,zh-cnandkoalong with thejaandenimage directories, and rewrites the documentation version token in the copied RST files. 1315 RST files and 192 images.versions.jsonmovesdevelopmentto 15.9.releasestays at 15.8, and neithersupportednorschedulechanges: 15.9 is not released, so it has no support window and no end-of-life date yet. This is the same shapeversions.jsonhad while 15.7 was the release and 15.8 was in development. The generatedeol.rsttables are unaffected, since they are built fromsupportedandschedule.Verification
15.8reference remains inside any 15.9 tree.install/is 3.8.0, which still matches<opensearch.version>in fess-parent on master, so no dependency version is carried over stale.python -m unittest discover -s tools,tools/update_eol.py --check, andtools/check_headings.pyover the 15.8 and 15.9 directories.Known, and deliberately left alone
The mechanical rewrite also renamed statements that record what changed in 15.8 — the
15.8 固有の移行作業/Changes in 15.8sections and roughly 250 similar lines across 14 files in the seven languages, such as "folded into the core in 15.8" and "the LLM features were split out in 15.8". Those now say 15.9 and are wrong.Correcting them is a content change that would be invisible inside a copy this large, so it is left to focused follow-up pull requests, the same way 15.8's content was corrected after #428.