Hello everyone,
We are updating the Eclipse JNoSQL versioning strategy to clarify how JNoSQL releases align with Jakarta EE generations.
From now on, the major version will indicate Jakarta EE compatibility. Minor and patch releases within the same major version will include backward-compatible improvements and new features.
Conceptually:
1.x.x → current Jakarta EE generation
2.x.x → next Jakarta EE generation
3.x.x → following Jakarta EE generation
This approach helps users easily identify the targeted Jakarta EE generation for each JNoSQL release, while allowing the project to continue following Semantic Versioning.
The documentation update is available in PR #801:
The original discussion and rationale are available in issue #793:
Next, we will apply this strategy to the Eclipse JNoSQL repositories and update branch names accordingly.
If you have questions or suggestions, please join the discussion in the issue. Contributions are welcome; you may open a PR to improve or clarify the documentation.
Thank you for helping us clarify Eclipse JNoSQL's release and compatibility model for the community.
