Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding 8.18 and 8.18.0 details, master not bumped as it's on 9.0.0, current still 8.17 #3161

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

eedugon
Copy link
Contributor

@eedugon eedugon commented Jan 30, 2025

This needs review as I have some concerns due to:

  • We have already master pointing to 9.0.0.
  • There's a comment on ECS about keeping it in 8.17.

Comments added in the code.

@eedugon eedugon requested a review from a team as a code owner January 30, 2025 09:37
Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@@ -1031,7 +1031,7 @@ contents:
prefix: en/ecs
# Please do not update current to 8.18
current: 8.17
Copy link
Contributor Author

@eedugon eedugon Jan 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lcawl , @bmorelli25 : I have a question here... are we going to keep ECS current in 8.17 even after releasing 8.18? why do we have that comment to not update current to 8.18? And why we don't have current = stackcurrent?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The ECS folks manage that book and just bumped it recently in #3157 it doesn't follow the same cadence as the other stack-versioned docs.

:major-version-only: 9
:ecs_version: 8.17
:ecs_version: 8.18
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here @lcawl , @bmorelli25 .

Also I have left master as 9.0 and only changed the references to 8.17 to 8.18. Let me know if this looks all right.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO you shouldn't need to touch master.asciidoc at all.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But master has this...

prev-major-last:        8.17

Shouldn't that line be bumped to 8.18?

@eedugon eedugon requested review from bmorelli25 and lcawl January 30, 2025 09:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants