Bug 1964918 - Clarification on version
Summary: Clarification on version
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Documentation
Version: rhacm-2.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: rhacm-2.2
Assignee: Christopher Dawson
QA Contact:
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks: mint
TreeView+ depends on / blocked
 
Reported: 2021-05-26 10:49 UTC by Pablo Iranzo Gómez
Modified: 2021-08-12 14:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-04 16:25:34 UTC
Target Upstream Version:
Embargoed:
ming: rhacm-2.2.z+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github open-cluster-management backlog issues 12844 0 None None None 2021-05-26 19:59:41 UTC

Description Pablo Iranzo Gómez 2021-05-26 10:49:10 UTC 
At https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.2/html-single/install/index

it says: "Note: Automatic upgrades do not span across major releases, for example, 2.1 to 2.2. To upgrade to the next major release, you must return to the OperatorHub page and select a new channel for the more current release."

I would understand that it should say "minor', as usually the format is:

MAJOR.MINOR.PATCH

Isn't it?
Comment 1 Mike Ng 2021-06-04 17:24:39 UTC 
G2Bsync 854855913 comment 
 cadawson Fri, 04 Jun 2021 16:24:23 UTC 
 G2Bsync
This update is now live in the documentation. Thank you.
Note You need to log in before you can comment on or make changes to this bug.