Schedule Of Releases - Bartan02/positive-health-int-team-2 GitHub Wiki
Schedule of Releases
Overview
Our project adheres to a structured release schedule to ensure a steady flow of improvements and features to our users while maintaining high standards of stability and quality. This section outlines our planned release cycles, including major, minor, and patch releases.
Release Frequency
- Major Releases: Scheduled at the end of the every sprint, these releases may introduce significant new features, breaking changes, or major improvements.
- Minor Releases: Minor releases is optional and scheduled only after the end of the project in case of resit's and fixes for upcomming exams.
- Patch Releases: Deployed as needed, patch releases address urgent bug fixes, security patches, and minor improvements to ensure the reliability and security of our software.
Upcoming Releases
| Version | Release Date | Key Features |
|---|---|---|
| 1.0.0 | 2023-12-04 | Implemented Activities and Authentication microservices, implemented API - Gateway. Fully designed home page, and login and register page |
| 2.0.0 | 2023-12-18 | Implemented map, friends microservices. |
| 3.0.0 | 2024-01-19 | Bug fixes, Implemented chat, friends, user profile microservices, finished product design |
| 3.0.1 | 2024-01-19 | Hotfix for calories calculation |
| 3.0.2 | 2024-01-19 | Hotfix not loading map |
| 3.0.3 | 2024-01-19 | Hotfix bug on activity results that there is more than 2 numbers after coma |
Release Process
- Planning: Each release cycle begins with a planning phase where new features, enhancements, and fixes are prioritized.
- Development: During this phase, the team works on implementing the planned features and improvements.
- Testing: Before a release, extensive testing is conducted to ensure functionality, performance, and compatibility.
- Deployment: The release is deployed, followed by monitoring to ensure smooth operation.
- Feedback: Post-release, we gather user feedback, which informs the planning of future releases.
Versioning
We follow Semantic Versioning (MAJOR.MINOR.PATCH) to keep our versioning clear and consistent:
- MAJOR version when we make incompatible API changes,
- MINOR version when we add functionality in a backward-compatible manner, and
- PATCH version when we make backward-compatible bug fixes.
Conclusion
Our release schedule is designed to balance the introduction of new features and improvements with the need for stability and reliability. We're committed to delivering quality software that meets the needs of our users while continuously iterating and improving our product.