-
Notifications
You must be signed in to change notification settings - Fork 60
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.
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
Create and define a release process for registry operator #1194
Create and define a release process for registry operator #1194
Comments
Candidate for demo at the end of Sprint 2247 |
Complexity sized: Aug 11, 2023 |
Created a draft for the versioning, currently following semver format: |
Blocked: #410 (comment) |
/kind task |
Applied revisions to release process proposal document to consider limitations of OpenShift CI triggering, use PRs to release branches to trigger testing and validation then use tag patterns for release image publication using the current GH workflows. |
#1326 adds the initial automation for the release process, therefore blocking this issue. |
|
Apply revisions to account for extra step for the OpenShift OperatorHub catalog publications: https://docs.openshift.com/container-platform/4.13/operators/operator_sdk/osdk-working-bundle-images.html#osdk-control-compat_osdk-working-bundle-images StepApply the following to the # OpenShift specific annotations.
com.redhat.openshift.versions: "v4.12-v4.13" |
No longer blocked: #1326 (comment) |
Initial release process document with versioning, release schedule, and release checklist has been defined https://docs.google.com/document/d/1olp6CwhHUMqGmaXXMLRn3z_S34Da4mdkLfm3k8DH-SM/edit. A release section under the registry operator's |
PR for adding release section to README is ready for review: devfile/registry-operator#70 |
Which area/kind this issue is related to?
/area registry
/area releng
Issue Description
Currently a release process for the registry operator does not exist, we will need one after cutting the first official release to continue a consist release cycle and versioning for releases.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: