Skip to content

[Docs] Reset release files for 9.0#199519

Merged
florent-leborgne merged 6 commits intoelastic:mainfrom
florent-leborgne:docs/reset-release-files-to-9
Nov 22, 2024
Merged

[Docs] Reset release files for 9.0#199519
florent-leborgne merged 6 commits intoelastic:mainfrom
florent-leborgne:docs/reset-release-files-to-9

Conversation

@florent-leborgne
Copy link
Copy Markdown
Member

This PR resets the release notes, upgrade notes, and what's new for 9.0.
It also cleans up a few references/files that were focusing on migration to 8.0

Some more PRs will happen to prepare the rest of the docs for v9

Closes: https://github.com/elastic/platform-docs-team/issues/564

@florent-leborgne florent-leborgne added Team:Docs release_note:skip Skip the PR/issue when compiling release notes v9.0.0 labels Nov 8, 2024
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/kibana-docs (Team:Docs)

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Nov 8, 2024

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.

@florent-leborgne florent-leborgne added the backport:skip This PR does not require backporting label Nov 8, 2024
…borgne/kibana; branch 'main' of github.com:elastic/kibana into docs/reset-release-files-to-9
@florent-leborgne florent-leborgne requested a review from a team November 21, 2024 10:41
Copy link
Copy Markdown
Contributor

@karenzone karenzone left a comment

Choose a reason for hiding this comment

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

WRT Breaking changes. Not all users are on the latest version, and we should support those users' upgrade paths, too. Should we keep the 8.0 breaking changes toward that goal?

Logstash has fewer breaking changes than ES or Kibana, but here's how we handle breaking changes: https://www.elastic.co/guide/en/logstash/current/breaking-changes.html#_breaking_changes_in_earlier_releases.

Breaking changes might be a candidate for the next round of IA projects.

@florent-leborgne
Copy link
Copy Markdown
Member Author

@karenzone good point. To upgrade to 9.0, users will have to upgrade to the last 8.x first. So in the upgrade docs we will call this out and link to the 8.x breaking change summary as well. That should help us keep only 9.x content in those files for that branch.

Copy link
Copy Markdown
Member

@kilfoyle kilfoyle left a comment

Choose a reason for hiding this comment

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

LGTM! 🦘

@florent-leborgne florent-leborgne merged commit e42569d into elastic:main Nov 22, 2024
paulinashakirova pushed a commit to paulinashakirova/kibana that referenced this pull request Nov 26, 2024
This PR resets the release notes, upgrade notes, and what's new for 9.0.
It also cleans up a few references/files that were focusing on migration
to 8.0

Some more PRs will happen to prepare the rest of the docs for v9

Closes: elastic/platform-docs-team#564
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this pull request Dec 12, 2024
This PR resets the release notes, upgrade notes, and what's new for 9.0.
It also cleans up a few references/files that were focusing on migration
to 8.0

Some more PRs will happen to prepare the rest of the docs for v9

Closes: elastic/platform-docs-team#564
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:Docs v9.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants