Big changes
Typically signals breaking compatibility after 1.0.
OSHAC AnalyticsSWIM CLUB PERFORMANCEQUICK GUIDE · VERSION NUMBERS
Why the numbers matter, and what they tell you about OSHAC Analytics.
Semantic Versioning uses three numbers: MAJOR.MINOR.PATCH. Think of them as the project's chapter, feature milestone and fix number.
Typically signals breaking compatibility after 1.0.
Marks a new milestone or addition.
Marks targeted corrections without new features.
For OSHAC: v0.3.0 means the dashboard is still evolving (0), this is its third feature milestone (3), and no follow-up patch has been numbered yet (0). This release includes the five training groups, navigation and a privacy-focused About page.
Before 1.0, features and interfaces can change more freely. A version number does not prove that security or production readiness has been audited.