Skip to content

Conversation

@amandalindsay
Copy link
Contributor

Add new 'static' compatibility table to show compatibility between Hazelcast Platform, its management and monitoring components, and clients.

Position in nav is TBC - temporarily under main versioning & compatibility topic

@netlify
Copy link

netlify bot commented Dec 11, 2025

Deploy Preview for hardcore-allen-f5257d ready!

Name Link
🔨 Latest commit e6d8067
🔍 Latest deploy log https://app.netlify.com/projects/hardcore-allen-f5257d/deploys/6941412b3956720008f6c2e8
😎 Deploy Preview https://deploy-preview-2035--hardcore-allen-f5257d.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@Rob-Hazelcast
Copy link
Contributor

Rob-Hazelcast commented Dec 16, 2025

https://docs.hazelcast.com/hazelcast/5.6/deploy/versioning-compatibility is the obvious home for this. Has most/all the same info already.

@hazelcast hazelcast deleted a comment from amandalindsay Jan 6, 2026
@jgardiner68
Copy link
Contributor

@Rob-Hazelcast Please update the table.

Needs a row for Platform 5.6.x, MC 5.9.0 and Operator 5.16.0 are the latest version

@Rob-Hazelcast
Copy link
Contributor

Not sure about this one. We have all the same info in https://github.com/hazelcast/hz-docs/pull/1998/changes in an easier to maintain format. We don't want statically maintained version numbers when we use variables everywhere else. And most of the table is effectively blank anyway.

Better for users to use the existing version info page and if for some reason they want to the info for more than one platform version they can change the version with the drop-down picker.

@Rob-Hazelcast
Copy link
Contributor

Superseded by #2056

@Rob-Hazelcast Rob-Hazelcast deleted the DOC-300-2 branch January 8, 2026 17:43
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.

3 participants