# πŸ› οΈ Maintenance & Support ## πŸ“¬ Support Channels | Topic | Channel | Response Time | | :---------------- | :------------------------------------------------ | :----------------- | | **Bug Reports** | GitHub Issues | 24–48 hours | | **Feature Ideas** | GitHub Discussions | Weekly review | | **Security** | [info@veriworkly.com](mailto:info@veriworkly.com) | Immediate priority | | **Questions** | Documentation | Self-service | --- ## πŸ“¦ Versioning This project follows **Semantic Versioning (SemVer)** for releases. ### Version Format ``` MAJOR.MINOR.PATCH ``` - **MAJOR** β†’ Breaking changes - **MINOR** β†’ New features (backward-compatible) - **PATCH** β†’ Bug fixes ### Where Versioning is Used Versioning is applied to **GitHub releases**. Example: - `v1.0.0` β†’ Initial stable release - `v1.1.0` β†’ New features added - `v1.1.1` β†’ Bug fixes > Releases are published in the GitHub β€œReleases” section. --- ## πŸ—ΊοΈ Roadmap The roadmap is available via the application and backend API. - Displays upcoming and planned features - Helps communicate project direction πŸ‘‰ Users can suggest ideas or improvements via **GitHub Discussions** > Roadmap items are maintained and prioritized by the core team. --- ## πŸ” Security If you discover a security vulnerability: - Do **not** open a public issue - Email: **[info@veriworkly.com](mailto:info@veriworkly.com)** We take security seriously and will respond with priority. --- Built by [VeriWorkly](https://veriworkly.com) with ❀️.