Release Process

Release Notes

When you make a PR to Atlas, a release notes change must be made to record your change or an explicit reason given why it is unnecessary. Unless the no changelog tag is present, the changelog-bot will leave an interactive comment on your PR. Please select the appropriate change type as listed in the comment.

Release Schedule

We aim to release as often as we can, so that the change set between releases is small. If you’d like a release candidate published for testing, please leave a comment on your PR.

Cutting for Release

From a PR, add the autorelease tag. When your PR is merged, the autorelease bot will automatically trigger a release and determine a version based on all change types since the previous release. If the PR has already merged and you are an AtlasDB maintainer, head to the internal autorelease page and trigger a release.

After a short wait (when the build at circleCI is successful) the artifacts will be published to Maven Central Repository. View them at the Maven Central AtlasDB page.