Skip to content

Design and document OLM V1 release process #112

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

Closed
Tracked by #123
dtfranz opened this issue Feb 1, 2023 · 0 comments
Closed
Tracked by #123

Design and document OLM V1 release process #112

dtfranz opened this issue Feb 1, 2023 · 0 comments
Assignees

Comments

@dtfranz
Copy link
Contributor

dtfranz commented Feb 1, 2023

We need to design and document the release process that will be followed for OLM V1. The process should be as simple and repeatable as possible; easily approachable by OLM V1 developers of all experience levels. The process should be fully documented and co-located with our release branch or repository as set in #111.

Acceptance criteria:

@awgreene awgreene changed the title Design and document release process Design and document OLM V1 release process Feb 8, 2023
@awgreene awgreene added this to OLM v1 Feb 16, 2023
@awgreene awgreene moved this to Todo in OLM v1 Feb 16, 2023
@awgreene awgreene moved this from Todo to In Progress in OLM v1 Mar 29, 2023
@dtfranz dtfranz closed this as completed Apr 3, 2023
@github-project-automation github-project-automation bot moved this from In Progress to Done in OLM v1 Apr 3, 2023
LalatenduMohanty pushed a commit to LalatenduMohanty/operator-controller that referenced this issue Dec 19, 2024
…#112)

to ensure we only list resources belonging to the 
`Catalog` resource currently being reconciled.
Signed-off-by: Bryce Palmer <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants