Skip to content

Commit 808b8cc

Browse files
chore: create release doc
1 parent 98bf325 commit 808b8cc

1 file changed

Lines changed: 19 additions & 0 deletions

File tree

RELEASE.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
# Release process for Core
2+
3+
## Manual
4+
5+
- Create a branch and update `Cargo.toml` (examples: `3.0.0-beta.1`, `3.0.0-rc.1`, `3.0.0`)
6+
- Push the branch (this should include change to `Cargo.toml` and `Cargo.lock`)
7+
- Create a PR and merge this release PR
8+
- Checkout main locally and pull the changes
9+
- Create annotated tag, eg. `git tag -a 'v3.0.0-0.beta.1' -m 'beta.1 release'`. There is a full explanation on what each of those digits mean is in `.circleci/packages/config.yaml`.
10+
This tag should match the regex as configured in `release-filter` in `.circleci/config.yml`
11+
- Once tagged, push it `git push origin v3.0.0-0.beta.1`
12+
- This should run the full build and publish the packages, a quick test will be to run a `curl`
13+
14+
e.g `curl https://dl.influxdata.com/influxdb/releases/influxdb3-core_x86_64-unknown-linux-gnu.tar.gz -o influxdb3-core_x86_64-unknown-linux-gnu.tar.gz -v`
15+
16+
untar the package and run `./influxdb3 --version` and the version should match what was set in `Cargo.toml`
17+
18+
19+
_At some point this should be scripted so that versions etc are in sync between the steps_

0 commit comments

Comments
 (0)