Version Policy
SocketIO4j Version Policy
socketio4j follows Semantic Versioning using the format:
x.y.z → MAJOR.MINOR.PATCHVersion Number Semantics
MAJOR (x)
Incremented when:
Breaking API changes are introduced
Protocol behavior changes
Major architectural redesigns occur
MINOR (y)
Incremented when:
New features or APIs are added
Backward compatibility is preserved
PATCH (z)
Incremented when:
Bug fixes are applied
Performance improvements are made
Internal refactors do not affect public APIs
Major Version Strategy
3.x – Compatibility Line
Maintains compatibility with the parent fork
Minimal divergence from upstream
Focused on stability and bug fixes
No major API redesigns
4.x – LTS Line (Upcoming)
Introduces new APIs and extended functionality
Includes architectural and performance improvements
Designed for production and enterprise use
Backward compatibility maintained within the 4.x line
Current status:
4.0.0is currently in SNAPSHOT and under active development. Once released as GA, 4.x will become the Long-Term Support (LTS) line.
5.x – Development Line (Planned)
Forward-looking and experimental
May introduce breaking changes
Rapid iteration and feature exploration
Not recommended for production use
Release Qualifiers
Pre-release versions are identified using postfix qualifiers before GA:
-SNAPSHOT
Active development, unstable
-M1, -M2
Milestone releases
-RC1, -RC2
Release candidates
(no postfix)
General Availability (GA)
Release Flow Example
Stability & Support Guarantees
GA releases are production-ready
Patch releases (
x.y.z) are backward compatibleMinor releases (
x.y) add features without breaking APIsMajor releases (
x) may introduce breaking changesLTS (4.x) will receive:
Critical bug fixes
Security updates
Long-term maintenance
SNAPSHOT versions should never be used in production
Milestone (
-M) and Release Candidate (-RC) versions are intended for validation and feedbackOnly GA releases are considered fully stable
Last updated
Was this helpful?