docs: Update documentation for OCM release process #208
Conversation
haoqing0110
force-pushed
the
br_release
branch
from
6e56b09 to
9af9390
Compare
|
/hold |
RELEASE.md
Outdated
|
|
||
| ### Patch Releases | ||
|
|
||
| The OCM patch release is expected to happen approximately a month after a minor release. Not all components are expected to have a minor release. Each component will perform a minor release based on the number of fixes needed from the community. |
There was a problem hiding this comment.
I thought that we release patch versions when needed. Will it be released regularly in the future? Please have confirm if it is "Not all components are expected to have a patch release?"
There was a problem hiding this comment.
Yes, there are some typos that should be patch release.
For the question of a regularly released patch releases, might need to discuss.
haoqing0110
force-pushed
the
br_release
branch
from
9af9390 to
508880a
Compare
Signed-off-by: Qing Hao <[email protected]>
haoqing0110
force-pushed
the
br_release
branch
from
508880a to
f4bc8f0
Compare
|
/assign @qiujian16 @mikeshng |
|
/unhold |
|
/approve /assign @mikeshng |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haoqing0110, mikeshng, qiujian16 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-merge-bot
bot
merged commit e04be25
into
open-cluster-management-io:main
Ref: #203
Based on the release.md @mikeshng wrote, just added some format and content.