Skip to content

Commit 02056dc

Browse files
authored
[DOCS] Update README.md
tweak backporting guidance
1 parent 81c23ca commit 02056dc

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -49,14 +49,14 @@ To re-run CI checks, an Elastic employee can select the `Re-run this job` option
4949

5050
> [!TIP]
5151
As of 9.0.0, we are currently only publishing from the `main` branch.
52-
**This means that backporting is currently not necessary for 9.0+ Elasticsearch docs.**
52+
We will continue to backport changes as usual, in case we need to revist this approach in the future.
5353

54-
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.
54+
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.
5555

5656
> [!NOTE]
5757
> If you need to make changes to 9.x docs and 8.x docs, you'll need to use two different workflows:
5858
59-
- **For `9.x` docs**, create a PR using the new Markdown system against the `main` branch.
59+
- **For `9.x` docs**, create a PR using the new Markdown system against the `main` branch and backport as necessary.
6060
- **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.
6161

6262
## Test code snippets

0 commit comments

Comments
 (0)