Versioning policy

Ridy follows a structured and predictable versioning strategy designed to provide stability, clarity, and flexibility for all levels of users — from independent developers to enterprise-grade deployments.

---

📌 Semantic Versioning (SemVer)

We use Semantic Versioning (SemVer) format:

MAJOR.MINOR.PATCH  →  e.g., 2.3.1

• MAJOR: Incompatible API or architecture changes (rare, typically once a year)
• MINOR: New features or service extensions that remain backward compatible
• PATCH: Bug fixes, UI adjustments, or minor enhancements

---

🔀 Server & Client Version Coordination

• Server-side and Client-side (Flutter apps) are versioned independently for MINOR and PATCH updates
• However, MAJOR versions are aligned across server and client to ensure compatibility and coherence
• Example:
  • Server 3.1.0 may still work with Driver App 3.0.2
  • But Server 4.x.x would expect compatible Client 4.x.x apps

---

📅 Release Cycle

Type	Frequency	Description
Major	~ Every 12 months	UI/UX redesigns, architecture updates
Feature	~ Every 3 months	New modules, service types, partner tools
Patch	As needed	Bug fixes, compatibility patches
Security Fixes	Immediate when needed	Delivered outside normal cycle if urgent

---

🔙 Backward Compatibility

• Backward compatibility is guaranteed for all MINOR and PATCH updates
• Rollback compatibility is not guaranteed, so always backup your server before upgrading
• Breaking changes, if any, are limited to MAJOR releases only

---

📣 Update Notifications

How You’ll Know About Updates:

• Codecanyon:
  • You’ll receive emails when new versions are published
  • Changelogs are listed on the Codecanyon item page
• Documentation Changelog Section:
  • You can refer to this documentation’s Changelog page for a full update history
• Website:
  Always check bettersuite.io for the latest product release announcements

---

🔧 Customizations & Updates

For Self-Managed Users:

• Use Version Control Systems (VCS) (e.g., Git) to manage your local customizations
• When updates are released, we recommend using:
  • git rebase or
  • git cherry-pick
    to integrate upstream changes into your customized codebase

For Pro Plus Plan Customers:

• Our team handles upgrades and conflict resolution internally
• Custom features are preserved where possible and adapted during version transitions.