Skip to content

docs: update release docs for v9 #16585

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

Closed
wants to merge 4 commits into from
Closed

docs: update release docs for v9 #16585

wants to merge 4 commits into from

Conversation

endorama
Copy link
Member

@endorama endorama commented Apr 9, 2025

Motivation/summary

Update release docs to account for the new doc structure. 9x and 8x releases are mostly similar so far, but they may diverge in the future. To account for this I split them in 2 separate files, so the execution flow is linear and does not have conditional branches based on version.

Checklist

For functional changes, consider:

  • Is it observable through the addition of either logging or metrics?
  • Is its use being published in telemetry to enable product improvement?
  • Have system tests been added to avoid regression?

How to test these changes

Review the docs (or follow them on the next release ;))

Related issues

#16181

@endorama endorama requested a review from a team as a code owner April 9, 2025 10:34
Copy link
Contributor

mergify bot commented Apr 9, 2025

This pull request does not have a backport label. Could you fix it @endorama? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-7.17 is the label to automatically backport to the 7.17 branch.
  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
  • backport-9./d is the label to automatically backport to the 9./d branch. /d is the digit.
  • backport-8.x is the label to automatically backport to the 8.x branch.
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

@endorama endorama added the backport-skip Skip notification from the automated backport with mergify label Apr 9, 2025
@endorama
Copy link
Member Author

endorama commented Apr 9, 2025

Not backporting as we leverage main docs for all releases.

Copy link
Member

@carsonip carsonip left a comment

Choose a reason for hiding this comment

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

also note that release notes do not need to be backported unless it is easier to do so, as docs will always be build from main.

@endorama
Copy link
Member Author

I forgot to set this to draft, the 9.x docs is not yet fully ready.

@endorama endorama marked this pull request as draft April 15, 2025 22:20
Copy link
Contributor

mergify bot commented Jun 30, 2025

This pull request is now in conflicts. Could you fix it @endorama? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b release-docs upstream/release-docs
git merge upstream/main
git push upstream release-docs

@endorama
Copy link
Member Author

Closed in favour of #17416

@endorama endorama closed this Jun 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-skip Skip notification from the automated backport with mergify
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants