NO-JIRA: docs - add versioning info #122
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@alebedev87: This pull request explicitly references no jira issue. In response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
|
/retest |
|
@alebedev87: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
|
||
| The AWS Load Balancer Operator's releases get published in two types of [OLM channels](https://olm.operatorframework.io/docs/glossary/#channel): the minor `release-vX.Y` and the major `release-vX`. | ||
|
|
||
| The minor channels contain patch releases. The major channels contain all patch releases from all minor channels. |
There was a problem hiding this comment.
I'm doubt if we should keep the major channels? I cannot see its use case, it that for upgrade automatically?
There was a problem hiding this comment.
is that for upgrade automatically?
Yes. The idea was to simplify the upgrade and to minimize the configuration on the client side. Since we often publish new minor channels (practically every new feature) the client has to change its subscription to explicitly mention new channel. Also, the OCP docs don't have to updated every time we publish a new feature.
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci
bot
added
the
lifecycle/stale
|
/remove-lifecycle stale |
openshift-ci
bot
removed
the
lifecycle/stale
This PR adds a new
versioning.mddoc which aims at explaining the current versioning, branching and support models of ALBO.