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

Alter Current Registry Operator Release Branch Name #1517

Open
2 tasks
Tracked by #1518
Jdubrick opened this issue Apr 11, 2024 · 0 comments
Open
2 tasks
Tracked by #1518

Alter Current Registry Operator Release Branch Name #1517

Jdubrick opened this issue Apr 11, 2024 · 0 comments
Labels
area/registry Devfile registry for stacks and infrastructure

Comments

@Jdubrick
Copy link
Contributor

Which area/kind this issue is related to?

/area registry

Issue Description

With the changes coming to the registry operator release process, we need to decide on whether to leave the current release branch, release-v0, named as such. Since we are moving to having a release branch for every release, such as v0.1.0 we either need to rename release-v0 to the latest release it contains, or leave it and start the naming convention at the next release.

Incoming changes to release process: #1516

Acceptance Criteria

  • Decide on what to do with release-v0 branch
  • Rename release-v0 OR close issue if applying new naming convention on next release
@openshift-ci openshift-ci bot added the area/registry Devfile registry for stacks and infrastructure label Apr 11, 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
Projects
Status: No status
Development

No branches or pull requests

1 participant