Add release document into repository by see-quick · Pull Request #69 · strimzi/test-container-images

see-quick · 2026-06-12T10:33:44Z

Type of change

Documentation

Description

This PR adds a release document to this repositorty. I reviewed it multiple times, so hopefully I didn't miss anything. Also as we need to always release both test-container and test-container-images repos I decided to put release documentation here ... as release process starts here. And then I can reference this document in the test-container repository.

Checklist

Update documentation
Update CHANGELOG.md (if present)
Reference relevant issue(s) and close them after merging
Write tests
Make sure all tests pass
Try your changes inside a Kubernetes cluster, not just from unit tests
AI assistance was used to create this PR (see the Strimzi AI policy)

Signed-off-by: see-quick <maros.orsak159@gmail.com>

scholzj

I left some comments. But to be honest, it seems rather lengthy and hard to follow. Instead of explaning the steps, it focus on commands which are semi-useless because they would not work for me. It is also completely missing the human part of the process we expect ... such as focus on the announcements, community testing, on some real (manual and/or exploratory) testing rather than 100% reliance on automated checks.

scholzj · 2026-06-12T21:38:24Z

+
+Create a release branch in **both** repositories:
+
+```bash


Should we just explain the branch name rather than provide command to copy with hardcoded remote names and directory names (in my case for example they are all different in practice, so the commands would be useless).

I would stick with the commands since they make it explicit what needs to be done, instead of relying on descriptive text.

I understand the concern about hardcoded remotes but if really neeeded , I can make it more generic it but overall I think the commands alone are enough for the reader to understand the intended approach.

I don't know. The problem with the commands is that they will not work for most people. So they are not really self explanatory in my opinion.

Adding info about how the versioning works is definitely worthy

Signed-off-by: see-quick <maros.orsak159@gmail.com>

see-quick · 2026-06-16T08:22:48Z

such as focus on the announcements, community testing, on some real (manual and/or exploratory) testing rather than 100% reliance on automated checks.

I will think about this and update the PR when I find more time.

Signed-off-by: see-quick <maros.orsak159@gmail.com>

Frawless

I think adding some short summary on the beggining of the doc might be useful as well? Like you will need to do this, this this, the detailed steps are the following... I understand this is quite complicated to make it released, but it is also not that simple to stay focused on the guide and short overview might improve it.

Frawless · 2026-07-07T19:27:32Z

+
+Create a release branch in **both** repositories:
+
+```bash


Adding info about how the versioning works is definitely worthy

Signed-off-by: see-quick <maros.orsak159@gmail.com>

see-quick · 2026-07-24T07:48:36Z

I think adding some short summary on the beggining of the doc might be useful as well? Like you will need to do this, this this, the detailed steps are the following... I understand this is quite complicated to make it released, but it is also not that simple to stay focused on the guide and short overview might improve it.

Updated.

Signed-off-by: see-quick <maros.orsak159@gmail.com>

see-quick · 2026-07-24T07:58:48Z

Let me know what you think @scholzj @Frawless.

such as focus on the announcements, community testing, on some real (manual and/or exploratory) testing rather than 100% reliance on automated checks.

I will think about this and update the PR when I find more time.

How do you see this? In 5. Release RC of test-container, there is already a note describing what to do after building the RC and where it should be announced.

scholzj · 2026-07-24T13:58:53Z

+RELEASE_VERSION=0.116.0 make release_maven release_json
+
+git add pom.xml src/main/resources/kafka_versions.json
+git commit -m "Set version to 0.116.0"


Suggested change

git commit -m "Set version to 0.116.0"

git commit -s -m "Set version to 0.116.0"

scholzj · 2026-07-24T14:00:07Z

+```bash
+git checkout release-0.116.x
+git cherry-pick <commit-hash>
+git push upstream release-0.116.x


Suggested change

git push upstream release-0.116.x

git push <repository> release-0.116.x

scholzj · 2026-07-24T14:01:25Z

+# test-container-images
+git checkout release-0.116.x
+git tag 0.116.0-rc1
+git push upstream 0.116.0-rc1


Suggested change

git push upstream 0.116.0-rc1

git push <repository> 0.116.0-rc1

scholzj · 2026-07-24T14:01:54Z

+cd ../test-container
+git checkout release-0.116.x
+git tag 0.116.0-rc1
+git push upstream 0.116.0-rc1


Suggested change

git push upstream 0.116.0-rc1

git push <repository> 0.116.0-rc1

scholzj · 2026-07-24T14:02:10Z

+# test-container-images
+git checkout release-0.116.x
+git tag 0.116.0
+git push upstream 0.116.0


Suggested change

git push upstream 0.116.0

git push <repository> 0.116.0

scholzj · 2026-07-24T14:02:16Z

+cd ../test-container
+git checkout release-0.116.x
+git tag 0.116.0
+git push upstream 0.116.0


Suggested change

git push upstream 0.116.0

git push <repository> 0.116.0

scholzj · 2026-07-24T14:04:19Z

+- Verify the GA images are available on [Quay.io](https://quay.io/organization/strimzi-test-container)
+- Verify the Maven artifact is available on [Maven Central](https://central.sonatype.com/artifact/io.strimzi/strimzi-test-container)
+- Create GitHub releases in both repositories
+- Bump the SNAPSHOT version on `main` in `strimzi/test-container` if needed


This is ideally somehting to do when you branch the release. Since fomr then on the main branch build might container things that will never reach the GA (so 0.5.0-SNAPSHOT might have things that never make the 0.5.0)

scholzj · 2026-07-24T14:05:19Z

+git push upstream 0.116.0
+```
+
+### 8. Post-release


Should the announcement be here as well? Maybe also suggest to open PRs for our own repos using the test container?

Add release document into repository

b9ca3d0

Signed-off-by: see-quick <maros.orsak159@gmail.com>

see-quick added this to the 0.117.0 milestone Jun 12, 2026

see-quick requested a review from a team June 12, 2026 10:33

see-quick self-assigned this Jun 12, 2026

see-quick added the documentation Improvements or additions to documentation label Jun 12, 2026

scholzj reviewed Jun 12, 2026

View reviewed changes

review from Jakub

5b48c31

Signed-off-by: see-quick <maros.orsak159@gmail.com>

less invasive command with release

f23102d

Signed-off-by: see-quick <maros.orsak159@gmail.com>

Frawless reviewed Jul 7, 2026

View reviewed changes

Jakub St. review

ae4342c

Signed-off-by: see-quick <maros.orsak159@gmail.com>

also update note about versiojning

931f721

Signed-off-by: see-quick <maros.orsak159@gmail.com>

scholzj reviewed Jul 24, 2026

View reviewed changes

	git commit -m "Set version to 0.116.0"
	git commit -s -m "Set version to 0.116.0"

	git push upstream release-0.116.x
	git push <repository> release-0.116.x

	git push upstream 0.116.0-rc1
	git push <repository> 0.116.0-rc1

Uh oh!

Conversation

see-quick commented Jun 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Type of change

Description

Checklist

Uh oh!

scholzj left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

see-quick commented Jun 16, 2026

Uh oh!

Frawless left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

see-quick commented Jul 24, 2026

Uh oh!

see-quick commented Jul 24, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

see-quick commented Jun 12, 2026 •

edited

Loading