Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
49 changes: 49 additions & 0 deletions RELEASE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
<!--
Copyright 2025 Columnar Technologies Inc.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->

# dbc Release Process

Since we rely on `goreleaser` and automation for managing our releases,
the actual release process is exceptionally easy:

```shell
$ git tag -a v0.2.0 -m "dbc v0.2.0 Release"
$ git push --tags
```

For pre-releases, we utilize tags such as `alpha` and `beta`. e.g., to
do a pre-release, you use the following command:

```shell
$ git tag -a v0.2.0-beta1 -m "dbc v0.2.0 Beta Release"
$ git push --tags
```

The automation will take over from the tag being pushed.

## Release Checklist

Before creating and pushing the tags, please consult the following
checklist of steps:

- [ ] Are the docs up to date with any new/changed features?
- [ ] Are the auto-complete scripts up to date with changes to the
options and subcommands?
- [ ] *(Before promoting a pre-release)* Has the pre-release been
manually tested?

Once the above checklist is completed, just push the new tag to
kick off the release process.
Loading