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.

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

Update Registry Operator Release Process & Automation #1518

Open
3 tasks
Jdubrick opened this issue Apr 11, 2024 · 0 comments
Open
3 tasks

Update Registry Operator Release Process & Automation #1518

Jdubrick opened this issue Apr 11, 2024 · 0 comments
Labels
area/registry Devfile registry for stacks and infrastructure kind/epic A high level requirement that can/should be split into smaller issues

Comments

@Jdubrick
Copy link
Contributor

Which area/kind this issue is related to?

/area registry

Issue Description

After working on #1326 it was discovered that the current release process for the devfile registry operator is presenting issues when trying to automate the tasks required to cut a release. Currently we are using release branches that represent a major version, such as release-v0, release-v1. This presents issues when we are trying to cut a new minor or patch release to the respective major where the base is coming from main. The automation runs into issues because of differing git histories between the release branch and main, resulting in manual merge resolution which defeats the purpose of automating the process. In order to prevent this from happening we need to adjust the release process to better fit our needs.

Acceptance Criteria

@Jdubrick Jdubrick added the kind/user-story User story for new enhancement label Apr 11, 2024
@openshift-ci openshift-ci bot added the area/registry Devfile registry for stacks and infrastructure label Apr 11, 2024
@johnmcollier johnmcollier added kind/epic A high level requirement that can/should be split into smaller issues and removed kind/user-story User story for new enhancement labels Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/registry Devfile registry for stacks and infrastructure kind/epic A high level requirement that can/should be split into smaller issues
Projects
Status: Backlog
Development

No branches or pull requests

2 participants