Skip to content

Release documentation update for order of releases #242

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sandeep-ctds merged 1 commit into from
Feb 18, 2026
Merged

Release documentation update for order of releases #242

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
14 changes: 14 additions & 0 deletions RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,22 @@ The project contains 3 different and independents artifacts:
3. KAAP Stack Chart

The releases process are independent. You can also do the release on a different branch and merge to main.
(**PR based**).
For reference, check [here.](https://github.com/datastax/kaap/pull/212)

## Release Order Guidance
This is not required to be followed if you are just releasing a new version for only one project.

### operator -> kaap → kaap-stack
To ensure `kaap-stack` is packaged with the latest `kaap` version and latest `operator` version.
This applies **only when a new `kaap` or `operator` version is part of the release cycle**.

This is also because `kaap-stack` uses a local dependency:
```yaml
repository: file://../kaap
```

A release is considered completed only when the PR is merged if we are doing a PR based approach.

## Operator image (datastax/kaap:latest)

Expand Down