Versioning and the release process#
We use semantic versioning (SemVer) for releases.
Frequency#
Releases are made approximately monthly.
Constraints and the release process#
Autoware has many repositories that are expected to work together.
When doing a release, we first make releases from sub-repositories such as autoware_core, autoware_universe, etc.
⚠️ The release version of Autoware is going to be same as the version of the newly released autoware_core.
ℹ️ The rest of the repositories can track their own versions.
Some repositories might not have changed at all, we can refer to their existing versions.
We will release all the required sub-repositories and update their references within the repositories/autoware.repos file.
We then test this system with various demos manually. And make sure the CI for the build passes.
Then we make an Autoware release.
Patches#
If there is a critical bug that needs to be fixed, we will make a patch release for the affected repositories.
Then we will go up a patch version release for Autoware.