Release Notes page for v9.x is too heavy — please bring back per-version pages

Meta Elastic
1

Hi,

I wanted to share some feedback about the release notes documentation structure that changed in v9.x.

What changed:
In v8.x, each version had its own dedicated page (e.g., 8.15, 8.16, 8.17), which made it easy to navigate directly to the version I needed. In v9.x, everything has been consolidated into a single page:

Problems I'm running into:

  • The page takes a long time to load due to the sheer amount of content
  • Scrolling is noticeably laggy after the page loads
  • Finding a specific version requires a lot of effort — anchor links help a little, but the experience is still frustrating compared to before

What I'd love to see:

  1. Bring back per-version pages like v8.x (strongly preferred)
  2. Or at minimum, add a version jump menu so users can navigate without scrolling through the entire history

The old structure was significantly more efficient for daily use. Is there a plan to improve this, or is there a workaround I'm not aware of?

Thanks!

2

Hi,

I agree wholeheartedly! While I can understand the goal to have everything on a single page the usability has clearly room for improvement.

I want to add that the Known issues are a mess too: In Kibana, Fleet and others, you cannot even see with oe glance which known issues affect your current version - you have to click each known issue

image
image754×542 43.2 KB

Best regards
Wolfram

3

Thanks so much for taking the time to give feedback on the docs @True and @Wolfram_Haussig. I've fed this back to @Kaarina_Tungseth and colleagues who look after the docs. We'll be in touch.

Thanks again!

4

Thank you for this feedback. We are currently in the process of re-designing the release notes experience, and learning how these structural changes affect your daily efficiency will directly inform our requirements. While we don't have a specific release date to share just yet, I can share that we are actively working on these changes now. If you have additional feedback and ideas on our current release notes, please keep them coming. Your input is helping us shape the future of Elastic documentation.