docs: add release process to the documentation - #356
Merged
Merged
Conversation
vsbogd
approved these changes
Sep 18, 2026
vsbogd
left a comment
vsbogd
left a comment
Member
There was a problem hiding this comment.
Looks good to me, thanks @janaina-senna !
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Add the Omega release process to the development documentation.
The documentation covers the complete release flow, from PR development and QA validation through the GitHub Release, release image build, approval steps, and final Docker image tag promotion.
It also documents the distinction between PR images and release images.
How Has This Been Tested?
This is a documentation-only change.
The documentation was reviewed for:
The documented process was cross-checked against the current release workflow configuration.
Checklist