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
1 of 3 tasks
Jdubrick opened this issue Apr 11, 2024 · 1 comment
Open
1 of 3 tasks

Update Registry Operator Release Process & Automation #1518

Jdubrick opened this issue Apr 11, 2024 · 1 comment
Assignees
Labels
area/registry Devfile registry for stacks and infrastructure devtools-week kind/epic A high level requirement that can/should be split into smaller issues lifecycle/stale Stale items. These items have not been updated for 90 days.

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
@Jdubrick Jdubrick moved this to Refinement in Devfile Project Apr 15, 2024
@Jdubrick Jdubrick removed the status in Devfile Project Apr 15, 2024
@Jdubrick Jdubrick moved this to Refinement in Devfile Project Apr 15, 2024
@johnmcollier johnmcollier added the kind/epic A high level requirement that can/should be split into smaller issues label Apr 17, 2024
@johnmcollier johnmcollier moved this from Refinement to Backlog in Devfile Project Apr 17, 2024
@johnmcollier johnmcollier removed the kind/user-story User story for new enhancement label Apr 17, 2024
@michael-valdron michael-valdron self-assigned this Aug 19, 2024
@michael-valdron michael-valdron moved this from Backlog to In Progress 🚧 in Devfile Project Aug 20, 2024
Copy link

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

@github-actions github-actions bot added the lifecycle/stale Stale items. These items have not been updated for 90 days. label Nov 27, 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 devtools-week kind/epic A high level requirement that can/should be split into smaller issues lifecycle/stale Stale items. These items have not been updated for 90 days.
Projects
Status: In Progress 🚧
Development

No branches or pull requests

3 participants