-
Notifications
You must be signed in to change notification settings - Fork 256
Update release-notes-elasticsearch-beta1.asciidoc #3024
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
Conversation
Caused by a bug that was fixed via elastic/elasticsearch#128050
A documentation preview will be available soon. Request a new doc build by commenting
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
couple minor things to take or leave :)
docs/en/install-upgrade/release-notes/release-notes-elasticsearch-beta1.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/install-upgrade/release-notes/release-notes-elasticsearch-beta1.asciidoc
Outdated
Show resolved
Hide resolved
Adding a small recommendation that we have always shared for major upgrades. If the user is already on the latest minor (8.18.x) it's also recommended to upgrade to 8.18.latest before upgrading to 9.x, as there could be fixes and improvements on upgrade assistant and other components. A clear example of this could be elastic/stack-docs#3024
FYI I have added that as a generic recommendation in our upgrade documentation, as it's what we have always recommended to users (if they are already in 8.18.x it's not mandatory, but always recommended to go to 8.18.LATEST before the major upgrade). reference: elastic/docs-content#1604 |
Adding a small recommendation that we have always shared for major upgrades. If the user is already on the latest minor (8.18.x) it's also recommended to upgrade to 8.18.latest before upgrading to 9.x, as there could be fixes and improvements on upgrade assistant and other components. A clear example of this could be elastic/stack-docs#3024 --------- Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
Caused by a bug that was fixed via elastic/elasticsearch#128050