Skip to content
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

Jump to bottom

Create and define a release process for registry operator #1194

Closed
5 tasks done
Tracked by #410
michael-valdron opened this issue Jul 17, 2023 · 13 comments · Fixed by devfile/registry-operator#70
Closed
5 tasks done
Tracked by #410

Create and define a release process for registry operator #1194

michael-valdron opened this issue Jul 17, 2023 · 13 comments · Fixed by devfile/registry-operator#70
Assignees
@michael-valdron
Labels
area/registry Devfile registry for stacks and infrastructure area/releng Release engineering demo Issue or PR candidate for a demo at the end of the Sprint devtools-week kind/task

Comments

@michael-valdron
Copy link
Member

michael-valdron commented Jul 17, 2023 •
edited

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

  • Define a release process for the registry operator
    • Versioning
    • Release schedule
    • Steps to complete release cut
  • Create a release section under README
@openshift-ci openshift-ci bot added area/registry Devfile registry for stacks and infrastructure area/releng Release engineering labels Jul 17, 2023
@michael-valdron michael-valdron mentioned this issue Jul 17, 2023
Closed
12 tasks
@michael-valdron michael-valdron self-assigned this Jul 18, 2023
@rm3l
Copy link
Member

rm3l commented Sep 18, 2023 •
edited

Candidate for demo at the end of Sprint 2247

@rm3l rm3l added the demo Issue or PR candidate for a demo at the end of the Sprint label Sep 18, 2023
@michael-valdron
Copy link
Member Author

Complexity sized: Aug 11, 2023
Time sized: Sep 22, 2023

@michael-valdron
Copy link
Member Author

Created a draft for the versioning, currently following semver format: v[major].[minor].[bugfix]

@michael-valdron
Copy link
Member Author

Blocked: #410 (comment)

@michael-valdron michael-valdron mentioned this issue Oct 18, 2023
Closed
3 tasks
@michael-valdron
Copy link
Member Author

/kind task

@michael-valdron
Copy link
Member Author

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.

@michael-valdron
Copy link
Member Author

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.

@michael-valdron
Copy link
Member Author

Removed from sprint plan until issue is unblocked upon completion of #1267 and #1326.

@michael-valdron
Copy link
Member Author

michael-valdron commented Nov 15, 2023 •
edited

Provide updates mentioned here: #1301 (comment) Update: No longer needed.

@michael-valdron
Copy link
Member Author

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

Step

Apply the following to the annotations.yaml bundle file upon opening a PR to https://github.com/redhat-openshift-ecosystem/community-operators-prod:

# OpenShift specific annotations.
com.redhat.openshift.versions: "v4.12-v4.13"

@michael-valdron michael-valdron mentioned this issue Nov 15, 2023
Closed
3 tasks
@michael-valdron
Copy link
Member Author

No longer blocked: #1326 (comment)

@michael-valdron
Copy link
Member Author

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 README.md is being worked on.

@michael-valdron michael-valdron mentioned this issue Dec 21, 2023
Merged
3 tasks
@michael-valdron
Copy link
Member Author

PR for adding release section to README is ready for review: devfile/registry-operator#70

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@michael-valdron michael-valdron

Labels
area/registry Devfile registry for stacks and infrastructure area/releng Release engineering demo Issue or PR candidate for a demo at the end of the Sprint devtools-week kind/task
Projects
Devfile Project
Status: Done ✅
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add releases section to README michael-valdron/devfile-registry-operator
2 participants
@rm3l @michael-valdron