Docs: Feedback for Hazelcast editions and distributions
- Dominant language
- No language data
- Stars
- 11
- Forks
- 112
- Avg merge
- 20h 29m
- Merged PRs (30d)
- 19
Description
Hi, I have some feedback about [this page](https://github.com/hazelcast/hz-docs/edit/main/docs/modules/getting-started/pages/editions.adoc)
It says in one of the Notes:
> Enterprise Edition features are marked with an Enterprise Edition label in this documentation. All pre-existing Hazelcast licenses, such as the Pro/Enterprise/Enterprise HD licenses, are valid for Hazelcast Platform. Each edition has its own installation file i.e. you can’t turn a Community Edition into an Enterprise Edition by adding a license key.
I know it is technically accurate because you have to have a different binary. However it could give an impression that you can't easily go from community to enterprise. In [this page](https://docs.hazelcast.com/hazelcast/5.7/migrate/rolling-restart) it talks about how to go about migrating from community to enterprise. Perhaps in the "editions" doc, in the note or around there, we could say - for more information about going from community to enterprise, see [here](https://docs.hazelcast.com/hazelcast/5.7/migrate/rolling-restart).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in docs/modules/getting-started/pages/editions.adoc and read the note describing edition binaries and licenses. Compare it with the migration guidance at migrate/rolling-restart, then add a clear reference for moving from Community Edition to Enterprise Edition. Done means the editions page links readers to the migration guidance without changing the technical statement.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 85/100