Atlantis follows a monthly release cadence to provide regular, predictable updates while maintaining stability for users.
- Frequency: Once per month
- Timing: First week OR last week of every month (but only once per month)
- Release Day: Typically Tuesday or Wednesday to allow for weekend buffer
Atlantis follows Semantic Versioning (SemVer):
- Major releases (x.0.0): Breaking changes
- Minor releases (0.x.0): New features, backward compatible
- Patch releases (0.0.x): Bug fixes and security patches
- Main branch: Contains the latest development work
- Release branches: Created for major/minor releases (e.g.,
release-0.20) - Hotfixes: Applied to both main and relevant release branches
- Release Announcements: Posted on GitHub Releases and community channels
- Breaking Changes: Clearly documented in release notes and migration guides
- Security Updates: Immediately communicated through security advisories
A release is ready when:
- ✅ All tests pass
- ✅ Documentation is updated
- ✅ Release notes are current
- ✅ No known critical bugs
- ✅ Security scan passes
- ✅ Performance benchmarks are acceptable
In case of critical security vulnerabilities or severe bugs:
- Immediate Assessment: Evaluate severity and impact
- Hotfix Development: Create targeted fix
- Expedited Testing: Focused testing on the fix
- Emergency Release: Release outside normal cadence if necessary
- Feature Requests: Submit early in the month for consideration
- Bug Reports: Report immediately for faster resolution
- Testing: Help test release candidates
- Documentation: Contribute to release notes and migration guides
For detailed information about contributing to Atlantis, see CONTRIBUTING.md.
For detailed information about past releases, see:
This document is maintained by the Atlantis maintainers. For questions about the release process, please open an issue or contact the maintainers.