github-mirrors/elasticsearch
1
0
Fork 0
mirror of https://github.com/elastic/elasticsearch.git synced 2025-04-19 04:45:07 -04:00
Code Issues Projects Releases Packages Wiki Activity

[DOCS] Update DOCS README.md backporting guidance (#124228)

Browse source
This commit is contained in:
Liam Thompson 2025-03-06 15:43:27 +01:00 • committed by GitHub
parent 04c8bf4ba8
commit 7cc613b0e4
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/README.md
View file

@ -49,14 +49,14 @@ To re-run CI checks, an Elastic employee can select the `Re-run this job` option
> [!TIP]
As of 9.0.0, we are currently only publishing from the `main` branch.
**This means that backporting is currently not necessary for 9.0+ Elasticsearch docs.**
We will continue to backport changes as usual, in case we need to revisit this approach in the future.
However, if you need to update the `8.x` docs, you'll have to use the old `asciidoc` system. Refer to the [`8.x` README](https://github.com/elastic/elasticsearch/blob/8.x/docs/README.asciidoc) for more information.
If you need to update the `8.x` docs, you'll have to use the old `asciidoc` system. Refer to the [`8.x` README](https://github.com/elastic/elasticsearch/blob/8.x/docs/README.asciidoc) for more information.
> [!NOTE]
> If you need to make changes to 9.x docs and 8.x docs, you'll need to use two different workflows:
- **For `9.x` docs**, create a PR using the new Markdown system against the `main` branch.
- **For `9.x` docs**, create a PR using the new Markdown system against the `main` branch and backport as necessary.
- **For `8.x` docs**, create a PR using the old AsciiDoc system against the `8.x` branch and backport the changes to any other `8.x` branches needed.
## Test code snippets