-
Notifications
You must be signed in to change notification settings - Fork 570
Define Upstream Release Process #2569
Copy link
Copy link
Open
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.triagedIssue has been considered by a member of the OLM communityIssue has been considered by a member of the OLM community
Milestone
Description
Metadata
Metadata
Assignees
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.triagedIssue has been considered by a member of the OLM communityIssue has been considered by a member of the OLM community
Feature Request
Is your feature request related to a problem? Please describe.
Please define an Operator Framework release process.
Describe the solution you'd like
As a member of the Operator Framework Community, it is difficult to know when a release will be cut or what will be included in the release. Ideally, the process should be consistent across all projects included in the Operator Framework. Some proposed requirements include:
I invite everyone to contribute additional requirements.